Agreed. I would say if a previously usable IO became unusable that is (on a case-by-case basis) a fine cause to block a release. Are the JIRAs filed?
On Thu, Jan 25, 2018 at 12:56 PM, Ismaël Mejía <ieme...@gmail.com> wrote: > I saw some recent reports on issues with CassandraIO that are not > blockers (not data loss) but IMO deserve to be included because > basically the issues imply that users cannot read from Cassandra in > parallel, and they were reported by production users. Probably a good > idea to finish these before the cut (they don't seem really hard to > fix), even if this implies to move the release cut one or two days. > > I also would like to volunteer to write the release blog post in > particular I would like to add a new section to thank the people that > contributed in this release as other projects do. > > On Thu, Jan 25, 2018 at 9:08 PM, Reuven Lax <re...@google.com> wrote: > > Thank you for running this JB! > > > > On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré <j...@nanthrax.net> > > wrote: > >> > >> Hi guys, > >> > >> Kenn and I are doing the latest triage. I'm creating some PRs that would > >> be good > >> for 2.3.0 (but not blocker). > >> > >> As discussed, I plan to start the release process tomorrow evening (my > >> time). > >> > >> Thanks ! > >> Regards > >> JB > >> > >> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré 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 > >> http://blog.nanthrax.net > >> Talend - http://www.talend.com > > > > >
