THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Meeting Minutes
Pending
Video Link:
| Widget Connector | ||
|---|---|---|
|
Agenda: Post agenda items below
- 4.0 status / check in / progress / ongoing work (added by Jordan West but anyone can lead this section)
- Call for volunteers to lead 4.0 quality tracks that need an owner
- 3.0 / 3.11 branch status
- Nate McCall: ApacheCon 2020
- Patrick McFadin: (Post meeting) Pacing and format of future meetings
Meeting Notes:
The community and contributors remain focussed on the 4.0 release. There was broad consensus that we want to keep working towards the 4.0 QA Test Plan and a call for contributors to sign up for major components. We also touched on a number of other process discussions and agreed to take a few discussions to the mailing list.
Action Items:
- All contributors: please sign up as either shepherds or contributors on the test plan. If we want 4.0 to happen we must get at least minimal coverage of these areas.
- Ahead of next call, review open tickets with “patch available” for Alpha and seek reviewers; for unassigned tickets, seek assignees or open discussion on scope.
- Discuss on dev list:
- Thread regarding when to branch for a post-4.0 release.
- Cadence of meeting: Consensus on call was “once a month, at an earlier time to enable more from European time zones to join - likely rotating.”
- Windows question: potentially a question to the user@ list if there are contributors willing to test / contribute patches for Windows.
- Jeremy Hanna: Discuss changes to defaults prior to 4.0 release.
- Patrick McFadin: Start discussion on dev list to settle time for next meetings and frequency.
- Anthony raising need for Reaper compatibility testing to other Reaper contributors; will note compatibility issues identified (in case they warrant a change in C* itself).
- Josh preparing JIRA epics that capture current headings in the Confluence “4.0 open issues” report.
Raw Notes (Joey Lynch):
Ongoing work in Test Plans
- Need people to step up for key components, especially things like
- (Jon Meredith) A number of important Read Repair needs coverage,
Some components we need help for?
- Coordinators, replication, read repair
- Metrics
- Tooling: External ecosystem
- Cluster setup/maintenance: ?
- Platforms/Runtimes : ?
- Cluster Upgrade: ?
- Documentation: ?
- Transient Replication: ?
Do we care about Windows production support?
- Will need a contributor to step up for this
- Some past precedent for releasing windows support after the main release
Discussion about how to ask the mailing list about windows usage ...
Documentation
- Dinesh and Deepak have gotten alot done here, a lot of copy has been written
- Joey can help review the patches and do copy editing
- Jon Haddad volunteered to review, Joey, Dinesh, Nate are also reviewing.
- Goal: inaccuracy should be removed before merge
- Vinay can take a look at a few of them, will get them
- Joey can fixup any diagrams we need made better
External tooling
- Sumanth and Joey can validate alpha cassandra-all integration with Priam, at least prove out it works, config, jmx, repair scheduling.
- Reaper: Some ongoing testing, will make a new major release so it’s all compatible
Should we be cutting releases more regularly regardless of what is in it?
- Some historical precedence for doing regular releases
- A bit of a trap because we run our own forks, a lot of users rely on releases to actually run the new versions
(Nate) ApacheCon 2020:
- RFC open until May: https://www.apachecon.com/acna2020/cfp.html
- Sept -> Oct in new orleans
- Not much more information, Nate will distill and summarize
- Goal to have a few more people reviewing
- More users attending for Cassandra track last year than anyone
- (Scott) we enjoyed the breakout discussions and space last year, can we have more flexibility in having breakout sections?
- (Nate) It was pretty strict last year, feedback given, we’re going to try to get it more flexible this time around
- Nate will try to push more for breakout space and conversations
- No guarantees since it is an external conference
- It was good to see Cassandra being a popular project, could potentially inject some $$ to have some more events.
- Some basic event things missing last time, like adapters, water, but we can get this right :-)
Other questions we should talk about?
- Quick ask, now is a good time to work on anything that touches configuration, metrics, logging or anything we need a dependency on
- Really nice if we can close out reviews on interface on anything that touches config, metrics, protocols
- (Sankalp)? Should we move this to 11am? Advantage is it will be more convenient for people in europe, new zealand will be 7am.
- (Nate): Let’s do a thread on it, we’ll just have to change it around, will have to go back and forth between APAC and Euro times
Should we branch and unfreeze trunk?
- Should get a mailing list discussion going
- Want to have an exit criteria based on deliverables rather than time
(Dinesh) Document for alpha -> beta - ga?
- Previous discussion had expectation is we can have a branch when we reach GA
- This was already discussed, but we can discuss it more
- Original idea was that 4.0 had to be stable enough before we can branch
- Could definitely revisit this decision
(Sankalp) People can work on branches, we just won’t focus on it
- Not branching doesn’t mean people can’t build features, we just can’t merge them yet
- Are we running out of work to stabilize 4.0?
- If anyone feels restricted, show the branch showing the problem
(Scott) Good one to bring up on the list
(Patrick) Final topic, is there anything we need to talk about in this format?
- Experiment, personally I like it because we can actually directly communicate, get discussions moving
- (Jordan) Having a very focused status conversation on 4.0 seems very beneficial
- Just need to get people working and prioritizing tickets tagged with 4.0-alphaX
- (Patrick) Just trying to put some order, please put an owner next to things that need discussing
- (Patrick) Pacing?
- Given the 4.0, once a quarter seems a long way
- (Scott) More people who can join and contribute development resources towards shipping 4.0
- (Patrick) is hearing 1/month is good but let’s pose on devlist
(Jeremy) Brought up tickets for this, sometimes people get the wrong idea about defaults
- Is it ok to fix up the defaults before 4.0
- E.g. token ranges default
- Why do we have a setting miset in the defaults?
- Yes, let’s get a thread going and get the decisions into the release lifecycle
- Does the change invalidate testing/validation or in the spirity
- Don’t have anything in the doc when defaults are changeable
- E.g. can we change defaults in alpha?
- E.g. tokens we test 32
- Automated testing all runs with 32
Chat Log
From Jeremy Hanna to Everyone1:07:57 PM
fwiw it’s not that late in Europe
From Jeff to Everyone1:08:45 PM
it's not business hours, though
From Jeremy Hanna to Everyone1:08:51 PM
this time range makes it convenient for those in Australia/New Zealand along with not too late in Europe
otherwise for Aus/NZ it’s going to be like 2 AM which isn’t business hours. but probably want to cover Europe more.
From sankalp to Everyone1:10:37 PM
we can move this 1 or 2 hours early
it will be 7 or 8am for NZ
8 or 9pm for EU
From Jeremy Hanna to Everyone1:11:16 PM
that would be fine imo as long as we can catch those in Europe. thanks Sankalp.
From Jeff to Everyone1:33:16 PM
anyone want to touch on timing to unlock trunk?
From Josh McKenzie to Everyone1:33:36 PM
Hm. That's an interesting one.
From Jeff to Everyone1:33:58 PM
i have no desire to unmute. but i think it's worth at least 30 seconds of chatting about when we unlock head
From Josh McKenzie to Everyone1:34:47 PM
Worth at least covering "should we open a thread on the dev list about this"
From Brandon Williams to Everyone1:34:53 PM
I'm a little surprised that 4.0 is not branched yet
because that is an indicator of being serious about release
From Jeff to Everyone1:35:59 PM
the counter argument is by not branching, you make merging fixes easier and make it harder to ignore the release in favor of new features landing on the new branch
From sankalp to Everyone1:36:13 PM
branching is NOT about being serious…it is the work done on the release to make it more stable
From dcapwell to Everyone1:36:16 PM
This is Jordan on David's machine. I think that used to be true in the past but this release cycle is different. The best way we can show progress on the release is to make progress on the tickets we have allotted to each milestone.
An informal meeting to create real-time collaboration for questions, issues and discussion. Meeting is held using Zoom, a video conferencing service. Please keep your microphone muted while not talking to keep ambient noise to a minimum. Zoom connection information is listed below.
...
Join Zoom Meeting
https://datastax.zoom.us/j/390839037
Meeting ID: 390 839 037
Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
888 475 4499 US Toll-free
877 853 5257 US Toll-free
+44 203 481 5240 United Kingdom
+44 131 460 1196 United Kingdom
+44 203 051 2874 United Kingdom
+44 203 481 5237 United Kingdom
0 800 260 5801 United Kingdom Toll-free
0 800 031 5717 United Kingdom Toll-free
+64 9 884 6780 New Zealand
+64 4 886 0026 New Zealand
0 800 527 544 New Zealand Toll-free
0 800 002 260 New Zealand Toll-free
+91 22 71 279 525 India
+91 80 71 279 440 India
+91 22 48 798 004 India
+91 224 879 8012 India
+91 22 62 192 563 India
000 800 050 5050 India Toll-free
000 800 040 1530 India Toll-free
+33 1 7037 2246 France
+33 1 7037 9729 France
+33 7 5678 4048 France
0 805 082 588 France Toll-free
0 800 940 415 France Toll-free
+49 30 5679 5800 Germany
+49 695 050 2596 Germany
+49 69 7104 9922 Germany
0 800 1800 150 Germany Toll-free
0 800 000 6954 Germany Toll-free
+55 21 3958 7888 Brazil
+55 11 4680 6788 Brazil
0 800 878 3108 Brazil Toll-free
0 800 282 5751 Brazil Toll-free
Meeting ID: 390 839 037
Find your local number: https://datastax.zoom.us/u/abESHyVHXk
Please try to post agenda items before the meeting to give potential participants time to prepare if needed.
Meetings will be recorded and posted on YouTube shortly after conclusion. The links will become part of the meeting minutes.
Meeting Minutes
Pending
Video Link:
| Widget Connector | ||
|---|---|---|
|
Agenda: Post agenda items below
- 4.0 status / check in / progress / ongoing work (added by Jordan West but anyone can lead this section)
- Call for volunteers to lead 4.0 quality tracks that need an owner
- 3.0 / 3.11 branch status
- Nate McCall: ApacheCon 2020
- Patrick McFadin: (Post meeting) Pacing and format of future meetings
Meeting Notes: