I would suggest following: 1. Announce some end date for 3.x new features. (To give sufficient time for community members to plan their feature contributions.) 2. 3.x to 4.x migration should happen on this date. 3. Community members can submit 3.x PRs till this date. 4. New PRs after this date should be for 4.x. 5. After this date, PRs for 3.x would be only for bug fixes. These fixes will have to be submitted to both 3.x, 4.x branches..
Giving sufficient time in #1 is important to avoid duplicate work in #5. In the meantime, community members can propose ideas for the 4.x. ~ Yogi On 1 September 2017 at 10:36, Pramod Immaneni <pra...@datatorrent.com> wrote: > Thomas, > > Wouldn't you need to call a separate procedural vote for whether changes > cannot be allowed into 3.x without requiring they be submitted to 4.x as > there was a disagreement there? Also, I am not sure that the procedural > vote argument can be used here for 4.x given that it involves modifications > to existing code. I would say we should drive towards getting a consensus > by addressing the concerns folks have about 4.x. > > On Thu, Aug 31, 2017 at 8:24 PM, Thomas Weise <t...@apache.org> wrote: > > > There wasn't any more discussion on this, so here is the result: > > > > 1. Version 4.0 as major version change from 3.x > > ==================================== > > > > +1 (7) > > > > Thomas Weise (PMC) > > Ananth G > > Vlad Rozov (PMC) > > Munagala Ramanath (committer) > > Pramod Immaneni (PMC) > > Sanjay Pujare > > David Yan (PMC) > > > > -1 (3) > > > > Amol Kekre (PMC) > > Sergey Golovko > > Ashwin Chandra Putta (committer) > > > > > > 2. Version 1.0 with simultaneous change of Maven artifact IDs > > =============================================== > > > > +1 (5) > > > > Thomas Weise (PMC) > > Ananth G > > Vlad Rozov (PMC) > > Munagala Ramanath (committer) > > David Yan (PMC) > > > > -1 (5) > > > > Pramod Immaneni (PMC) > > Sanjay Pujare > > Amol Kekre (PMC) > > Sergey Golovko > > Ashwin Chandra Putta (committer) > > > > > > RESULT > > ======= > > > > Vote for option 1 (major version 4.x) *passes* with majority rule [1]. > > > > Thanks, > > Thomas > > > > > > [1] https://www.apache.org/foundation/voting.html > > > > > > On Mon, Aug 21, 2017 at 6:39 PM, Thomas Weise <t...@apache.org> wrote: > > > > > This is to formalize the major version change for Malhar discussed in > > [1]. > > > > > > There are two options for major version change. Major version change > will > > > rename legacy packages to org.apache.apex sub packages while retaining > > file > > > history in git. Other cleanup such as removing deprecated code is also > > > expected. > > > > > > 1. Version 4.0 as major version change from 3.x > > > > > > 2. Version 1.0 with simultaneous change of Maven artifact IDs > > > > > > Please refer to the discussion thread [1] for reasoning behind both of > > the > > > options. > > > > > > Please vote on both options. Primary vote for your preferred option, > > > secondary for the other. Secondary vote can be used when counting > primary > > > vote alone isn't conclusive. > > > > > > Vote will be open for at least 72 hours. > > > > > > Thanks, > > > Thomas > > > > > > [1] https://lists.apache.org/thread.html/bd1db8a2d01e23b0c0ab98a > 785f6ee > > > 9492a1ac9e52d422568a46e5f3@%3Cdev.apex.apache.org%3E > > > > > >
