+1 to get 2.5 out asap (fixes blockers so always good to let it be upgraded) +1000 to split beam releases (and even repos) by concerns
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> 2018-04-06 10:48 GMT+02:00 Jean-Baptiste Onofré <j...@nanthrax.net>: > Hi guys, > > Apache Beam 2.4.0 has been released on March 20th. > > According to our cycle of release (roughly 6 weeks), we should think about > 2.5.0. > > I'm volunteer to tackle this release. > > I'm proposing the following items: > > 1. We start the Jira triage now, up to Tuesday > 2. I would like to cut the release on Tuesday night (Europe time) > 2bis. I think it's wiser to still use Maven for this release. Do you think > we > will be ready to try a release with Gradle ? > > After this release, I would like a discussion about: > 1. Gradle release (if we release 2.5.0 with Maven) > 2. Isolate release cycle per Beam part. I think it would be interesting to > have > different release cycle: SDKs, DSLs, Runners, IOs. That's another > discussion, I > will start a thread about that. > > Thoughts ? > > Regards > JB > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
