Hi Udi, (Question) I started learning how Beam dependencies are maintained through releases. https://beam.apache.org/contribute/dependencies/ says
*Beam community has agreed on following policies regarding upgrading dependencies.* ... *A significantly outdated dependency (identified manually or through the automated Jenkins job) should result in a JIRA that is a blocker for the next release. Release manager may choose to push the blocker to the subsequent release or downgrade from a blocker.* Is the statement above still valid? We have ~250 automatically created tickets [1] for dependency upgrade. [1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20dependencies%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC Regards, Tomo On Wed, Nov 20, 2019 at 3:48 PM Udi Meiri <eh...@google.com> wrote: > Hi all, > > The next (2.18) release branch cut is scheduled for Dec 4, according to > the calendar > <https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com> > . > I would like to volunteer myself to do this release. > The plan is to cut the branch on that date, and cherrypick release-blocking > fixes afterwards if any. > > Any unresolved release blocking JIRA issues for 2.18 should have their > "Fix Version/s" marked as "2.18.0". > > Any comments or objections? > > -- Regards, Tomo
