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]
