One of the main shifts that I think helped this release was explicitly not being feature driven, rather releasing what's already in the branch. That doesn't mean it's not a good call to action to try and get long-pending PRs or similar wrapped up.
On Tue, Feb 20, 2018 at 2:10 PM, Romain Manni-Bucau <[email protected]> wrote: > There are a lot of long pending PR, would be good to merge them before 2.4. > Some are bringing tests for the 2.3 release which can be critical to > include. > > Maybe we should list the pr and jira we want it before picking a date? > > Le 20 févr. 2018 22:02, "Konstantinos Katsiapis" <[email protected]> a > écrit : >> >> +1 since tf.transform 0.6 depends on Beam 2.4 and Tensorflow 1.6 (and the >> latter already has an RC out, so we will likely be blocked on Beam). >> >> On Tue, Feb 20, 2018 at 12:50 PM, Robert Bradshaw <[email protected]> >> wrote: >>> >>> Now that Beam 2.3.0 went out (and in record time, kudos to all that >>> made this happen!) It'd be great to keep the ball rolling for a >>> similarly well-executed 2.4. A lot has gone in [1] since we made the >>> 2.3 cut, and to keep our cadence up I would propose a time-based cut >>> date early next week (say the 28th). >>> >>> I'll volunteer to do this release. >>> >>> [1] https://github.com/apache/beam/compare/release-2.3.0...master >> >> >> >> >> -- >> Gus Katsiapis | Software Engineer | [email protected] | 650-918-7487
