At this point it's taken over three weeks to resolve release-blocking issues, and there are still some remaining. Monday morning I will go ahead and cut an initial release candidate, so we get a snapshot to base on. The remaining blocking issues will either be cherry picked into an additional release candidate or punted to 2.3.0, depending on severity.
Reuven On Wed, Sep 20, 2017 at 5:34 AM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Reuven, > > thanks for the update. I will pick up some Jira in my bucket (to > verify/double check or implement). > > Regards > JB > > > On 09/20/2017 04:23 AM, Reuven Lax wrote: > >> There are 7 issues left on >> https://issues.apache.org/jira/projects/BEAM/versions/12341044 after I >> moved some items to 2.3.0 if they appeared to not need to be in 2.2.0 >> (some >> were originally slated for 2.1.0, and there was no apparent progress on >> them). Please object if you feel that it's important that any of these be >> in 2.2.0 >> >> Of the remaining issues, three (BEAM-2956, BEAM-2298, BEAM-2271) appear to >> already be fixed; please verify this and close the issue if you are the >> reporter. The remaining issues (BEAM-2834, BEAM-2858, BEAM-2870, >> BEAM-29540) all have outstanding pull requests. As soon as all of these >> pull requests are merged, I will start the release cut. >> >> Reuven >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
