+1 Thank you Udi！ Best， Jincheng
Valentyn Tymofieiev <[email protected]>于2019年11月28日 周四08:09写道： > +1. Thanks, Udi! > > On Wed, Nov 27, 2019 at 12:58 PM Ahmet Altay <[email protected]> wrote: > >> Thank you Udi for keeping the release cadence. +1 to cutting 2.18.0 >> branch on time. >> >> On Thu, Nov 21, 2019 at 10:07 AM Udi Meiri <[email protected]> wrote: >> >>> Thanks Cham. Tomo, if there are any dependencies you believe are >>> blockers please mark them. >>> Also, only the sub-tasks >>> <https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20issuetype%20in%20subTaskIssueTypes()%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20dependencies%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC> >>> seem to be real upgrade tickets (so only ~150). >>> >>> Back to the original intent of my message, do we have consensus on who >>> will do the 2.18 release? >>> >>> On Wed, Nov 20, 2019 at 6:05 PM Tomo Suzuki <[email protected]> wrote: >>> >>>> Thank you for response. >>>> >>>> On Wed, Nov 20, 2019 at 16:49 Chamikara Jayalath <[email protected]> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Nov 20, 2019 at 1:04 PM Tomo Suzuki <[email protected]> >>>>> wrote: >>>>> >>>>>> 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. >>>>>> >>>>> >>>>> I think it's up to the release manager as mentioned in the statement. >>>>> We surely don't want to block releases by all these JIRAs but Beam >>>>> community and/or release manager may decide to make some of these blockers >>>>> if needed. >>>>> I don't think the tool automatically makes the auto generated JIRAs >>>>> release blockers. >>>>> >>>>> Thanks, >>>>> Cham >>>>> >>>>> >>>>>> [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 <[email protected]> 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 >>>>>> >>>>> -- >>>> Regards, >>>> Tomo >>>> >>>
