Re: [PROPOSAL] Preparing for Beam 2.26.0 release
+1 Thanx! On Wed, Oct 28, 2020 at 7:14 AM Valentyn Tymofieiev wrote: > +1, thanks and good luck! > > On Tue, Oct 27, 2020 at 1:59 PM Tyson Hamilton wrote: > >> Thanks Rebo! SGTM. >> >> On Tue, Oct 27, 2020 at 11:11 AM Udi Meiri wrote: >> >>> +1 sg! >>> >>> On Tue, Oct 27, 2020 at 10:02 AM Robert Burke wrote: >>> Hello everyone! The next Beam release (2.26.0) is scheduled to be cut on November 4th according to the release calendar [1]. I'd like to volunteer myself to handle this release. I plan on cutting the branch on November 5th (since I've had November 4th booked off for months now) and cherry-picking in release-blocking fixes afterwards. So unresolved release blocking JIRA issues should have their "Fix Version/s" marked as "2.26.0". Any comments or objections? Thanks, Robert Burke @lostluck [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com >>>
Re: [PROPOSAL] Preparing for Beam 2.26.0 release
+1 sg! On Tue, Oct 27, 2020 at 10:02 AM Robert Burke wrote: > Hello everyone! > > The next Beam release (2.26.0) is scheduled to be cut on November 4th > according to the release calendar [1]. > > I'd like to volunteer myself to handle this release. I plan on cutting the > branch on November 5th (since I've had November 4th booked off for months > now) and cherry-picking in release-blocking fixes > afterwards. So unresolved release blocking JIRA issues should have > their "Fix Version/s" marked as "2.26.0". > > Any comments or objections? > > Thanks, > Robert Burke > @lostluck > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com > smime.p7s Description: S/MIME Cryptographic Signature
[PROPOSAL] Preparing for Beam 2.26.0 release
Hello everyone! The next Beam release (2.26.0) is scheduled to be cut on November 4th according to the release calendar [1]. I'd like to volunteer myself to handle this release. I plan on cutting the branch on November 5th (since I've had November 4th booked off for months now) and cherry-picking in release-blocking fixes afterwards. So unresolved release blocking JIRA issues should have their "Fix Version/s" marked as "2.26.0". Any comments or objections? Thanks, Robert Burke @lostluck [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com
