As I wrote, we did have examples of changes + cascading, it is okay. But I don't agree with your statement about the board, as they themselves state "should" not "must" for 72h. If it does not cut with them, they should modify the refd page(s).
And it's not "we're impatient" either, part of the response for that is in "hasty changes" canned response. Simply put: - people see releases as a chore, as some "burden" that needs to be done once in a while (see refd Slack messages in 1st mail), and when it comes to be done, "let's do it when it's worth". We have MANY user questions on ML of type "when is X released? As the issue [the user is interested in] is fixed". And we have too many "dropped balls" in our court. IMHO, modifying the process (to take less than 72+2h) is one step toward making release less painful, less blocker. Fun fact: maven project consists of (not sure of exact count, just guessing) 150+ repositories (GH on ASF org gives 153 when I type in "maven-" in the repo search bar). This is a LOT. If we'd, for some reason, start releasing all of those in 72h windows, it would be 10800 hours, or 450 days, more than a year. On Fri, Nov 18, 2022 at 8:34 PM David Jencks <[email protected]> wrote: > Which developers have to pause what activities? > > From previous discussions elsewhere, I’m strongly of the opinion that < 72 > hr release votes are intended only for emergency security fixes and similar > events, and that “we’re impatient” isn’t going to cut it with the board. > It certainly wouldn’t with me. > > How many of these annoyances would be eliminated by an easy way to release > and vote on a set of changed artifacts + the cascading dependencies all at > once? > > thanks > David Jencks > > > On Nov 18, 2022, at 11:17 AM, Tamás Cservenák <[email protected]> > wrote: > > > > David, > > > > I just meant that there is a "forced pause" of 72h. > > > > T > > > > On Fri, Nov 18, 2022 at 7:50 PM David Jencks <[email protected]> > > wrote: > > > >> +1 from the sidelines. > >> > >> I don’t understand > >>>>> * current process causes (forced) context switching, and can likely > >> lead to > >> human mistakes: when the release vote is announced, developer is FORCED > to > >> stop for 72h and possibly switch. This is just a productivity killer. > >> <<< > >> Who is forced to do anything and for what reason? > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
