I think we should triage things to have no set FixVersion instead of 2.4.0. If we haven't done it since last time then it isn't actually a priority.
I think that we should avoid placing a FixVersion on a JIRA except in two cases: - it is resolved so you are recording it for automated changelog - it is a currently active data loss bug that means Beam is not safe to release This will help to speed up release cadence so it isn't such a big deal to squeeze things in. Kenn On Tue, Jan 23, 2018 at 3:15 PM, Lukasz Cwik <lc...@google.com> wrote: > I fear that this list has been the "priority" list for bug fixes and > dropping the fix version will lose this information. I would be open for a > new label if we really wanted to change this but labels can be forgotten > about as well. > > On Tue, Jan 23, 2018 at 3:06 PM, Alan Myrvold <amyrv...@google.com> wrote: > >> Are there improvements to the release process to make the triaging of >> open issues easier? >> >> I see 30 unresolved issues with fixVersion 2.3.0 in >> https://issues.apache.org/jira/browse/BEAM-3160?jql=proje >> ct%20%3D%20BEAM%20AND%20status%20%3D%20Open%20AND%20fixVersi >> on%20%3D%202.3.0%20ORDER%20BY%20updated%20DESC >> >> The release process, https://beam.apache.org/contri >> bute/release-guide/#create-a-new-version-in-jira >> indicates that all these issues will be moved to 2.4.0 if they are not >> resolved. Would it be better to unset the fixVersion for any issues that >> aren't fixed instead of moving them to the next version? >> >> On Tue, Jan 23, 2018 at 12:16 PM, Jean-Baptiste Onofré <j...@nanthrax.net> >> wrote: >> >>> Awesome ! >>> >>> Ready to review if you want ! >>> >>> Regards >>> JB >>> >>> On 23/01/2018 20:48, Eugene Kirpichov wrote: >>> >>>> Regarding Java 8, I'm about to send a large mechanical PR converting a >>>> lot of code to use lambdas and better type inference. >>>> >>>> On Tue, Jan 23, 2018 at 11:37 AM Jean-Baptiste Onofré <j...@nanthrax.net >>>> <mailto:j...@nanthrax.net>> wrote: >>>> >>>> By the way, I would like to complete the Java 8 support (the >>>> subtasks in >>>> the main Java 8 Jira). So, let me try to move forward on this. >>>> >>>> Regards >>>> JB >>>> >>>> On 23/01/2018 19:51, Reuven Lax wrote: >>>> > Sounds good. Also many things that are currently flagged as 2.3.0 >>>> don't >>>> > appear to be actual release blockers to me. >>>> > >>>> > On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré >>>> <j...@nanthrax.net <mailto:j...@nanthrax.net> >>>> > <mailto:j...@nanthrax.net <mailto:j...@nanthrax.net>>> wrote: >>>> > >>>> > Hi guys, >>>> > >>>> > Some days ago, I proposed to start Beam 2.3.0 around January >>>> 26th. >>>> > So, we are >>>> > few days from this date. >>>> > >>>> > As a best effort, can you please in Jira flag the Jira with >>>> fix >>>> > version 2.3.0 >>>> > and blocker for the release. Then, I will know when I can >>>> start the >>>> > release process. >>>> > >>>> > Thanks ! >>>> > >>>> > Regards >>>> > JB >>>> > -- >>>> > Jean-Baptiste Onofré >>>> > jbono...@apache.org <mailto:jbono...@apache.org> >>>> <mailto:jbono...@apache.org <mailto:jbono...@apache.org>> >>>> > http://blog.nanthrax.net >>>> > Talend - http://www.talend.com >>>> > >>>> > >>>> >>>> >> >
