Prasanna, It seems to me our largest concern is that the impending 4.2 code freeze will create a priority conflict between stabilizing 4.1 and completing 4.2 features (including reviews). Would it be acceptable to push back the 4.2 until say two weeks after the first 4.1 RC ships? With this type of delay, we could pend merge reviews where we have resource contention between 4.1 stabilization and 4.2 development. This approach would also give us a reasonable bit of time to rebase and integration test any intervening 4.1 changes into master.
Thanks, -John On May 21, 2013, at 1:43 AM, Prasanna Santhanam <t...@apache.org> wrote: > On Mon, May 20, 2013 at 04:34:58PM -0400, Chip Childers wrote: >> All, >> >> I can't help but notice that we continue to have features being developed and >> proposed / merged into master while I struggle to get opinions / help on >> 4.1. I doubt that we (as a community) want to abandon 4.1, but I can't >> be certain. >> >> Should we abandon an attempt at releasing 4.1, and instead move on to >> 4.2? This wouldn't solve any of the blocker bugs holding up 4.1 >> though... >> >> Instead, should we hold off on all merges of new features into master until >> 4.1 is complete? This might allow us to refocus as a community to >> complete the current release goal, but would obviously impact folks that >> are working on new features (although your help in completing 4.1 would >> be useful). >> > > My concern is that features are merging in to master at a rapid pace > while part of the community is focussed on 4.1. Many merges passed > lazy consensus in the past weeks. So I don't know if people on 4.1 > have had enough time to look through the patches and merge requests in > detail. > > Should the freeze for 4.2 be postponed thereby allowing time to get > 4.1 out the door? > > -- > Prasanna., > > ------------------------ > Powered by BigRock.com >
