Thinking out loud: why not trying a 2.3.1 with small fixes only and the 2.4 after 6 weeks starting from the 2.3.0 real release date.
Le 28 févr. 2018 04:24, "Jean-Baptiste Onofré" <[email protected]> a écrit : > OK, maybe I wasn't clear: for me the cycle is ~ 6 weeks once a release is > out, > not when it started. > > I don't remember about monthly release (it's too fast IMHO). > > Anyway, let me find the thread dealing with release pace and propose a > clear > statement. It's important for our users. > > Regards > JB > > On 02/28/2018 04:17 AM, Reuven Lax wrote: > > It's been six weeks since you proposed beam 2.3.0. so assuming the same > time > > scale for this release, that's 1.5 months between releases. Slightly > faster than > > 2 months, but not by much. > > > > I do seem to remember that the original goal for beam was monthly > releases though. > > > > Reuven > > > > On Tue, Feb 27, 2018, 9:12 PM Jean-Baptiste Onofré <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi Reuven, > > > > In a previous thread (about Beam project execution), I proposed a > release every > > two months (as a best effort), I will find the e-mail. > > > > Beam 2.3.0 has been released "officially" on February 16th, so two > week ago > > roughly. I would have expected 2.4.0 not before end of March. > > > > If we have issue we want to fix fast, then 2.3.1 is good. If it's a > new release > > in the pace, it's pretty fast and might "confuse" our users. > > > > That's why I'm curious ;) > > > > Regards > > JB > > > > On 02/28/2018 03:50 AM, Reuven Lax wrote: > > > Wasn't the original statement monthly releases? We've never > realistically > > > managed that, but Robert's proposed cut will be on a 6-week pace. > > > > > > On Tue, Feb 27, 2018, 8:48 PM Jean-Baptiste Onofré < > [email protected] > > <mailto:[email protected]> > > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > > > Hi Robert, > > > > > > I'm just curious: it's pretty fast compared to the original > plan of a > > release > > > every two months. What's the reason to cut 2.4.0 now instead > of end of > > March ? > > > > > > I will do the Jira triage and update today. > > > > > > Regards > > > JB > > > > > > On 02/27/2018 09:21 PM, Robert Bradshaw wrote: > > > > I'm planning on cutting the 2.4.0 release branch soon > (tomorrow?). I > > see 13 > > > > open issues on JIRA [1], none of which are labeled as > blockers. If there > > > > are any that cannot be bumped to the next release, let me > know soon. > > > > > > > > - Robert > > > > > > > > > > > > [1] > > > > > > > > > https://issues.apache.org/jira/browse/BEAM-3749?jql= > project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20% > 22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%202.4.0 > > > > > > > > > > -- > > > Jean-Baptiste Onofré > > > [email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>> > > > http://blog.nanthrax.net > > > Talend - http://www.talend.com > > > > > > > -- > > Jean-Baptiste Onofré > > [email protected] <mailto:[email protected]> > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
