Some of us met in Google Meet at 10AM EDT on 8/23 to discuss ideas for near future accumulo releases and development. This was linked in our #accumulo Slack channel. For those who weren't able to make the meeting, here's what we discussed doing:
GitHub updates (to make elasticity work part of our mainline development): * Create a 3.1 branch from current main * Update main PRs to point to 3.1 * Merge elasticity into main * Update elasticity PRs to point to main 2.1 plans: * Possibly consider a 2.2 LTM to supersede 2.1? * Reduce work on 2.1 by limiting ourselves to critical bugs * Create a utility to help analyze bulk V2 uses 3.1 plans: * Triage 3.1 tickets to finalize feature set * Plan a non-LTM or LTM release? (unclear would be more suitable) * also triage API changes as a bridge release for elasticity 4.0 plans: * Plan a 4.0.0-alpha-1 for elasticity changes out of main (soon-ish, but not immediately) * Update accumulo-testing to support elasticity Of these, the only immediate actions we're planning on taking is the branching in the "GitHub updates" section above. Both Dave Marion and Christopher Tubbs said they'd be willing to do this, and will coordinate to make sure they don't step on each other's toes... basically whoever gets to it first. The plan is to do this by early next week.
