On Mon, Jan 7, 2019 at 11:51 AM Alex Harui <aha...@adobe.com.invalid> wrote: > > > > On 1/7/19, 11:38 AM, "Roman Shaposhnik" <ro...@shaposhnik.org> wrote: > > On Mon, Jan 7, 2019 at 11:33 AM Alex Harui <aha...@adobe.com.invalid> > wrote: > > > > > > > > On 1/7/19, 11:05 AM, "Roman Shaposhnik" <ro...@shaposhnik.org> wrote: > > > > On Mon, Jan 7, 2019 at 11:00 AM Alex Harui > <aha...@adobe.com.invalid> wrote: > > > > > > Hi Mike, > > > > > > Thanks for the input. IMO, that exploit would be easily seen. > The release plugin should only be changing one-liners with version numbers. > > > > If this is all it ever does I still don't understand why a human > > operator won't suffice. > > > > Because our humans have been unable to get their computers to work. > > They seem to be having network reliability issues. So if I can provision > > a machine to work that others can use to cut releases, it will save us > time and encourage others to become RMs. > > With all due respect, the above sounds like a really *weird* reason to > make *others* > do the work for you. > > I don't understand. Who am I "making" do what work?
INFRA > And why do at least 3 others want something similar? I don't know -- I haven't heard those arguments. > And what would you propose Royale should do instead? Always have me cut > releases? I suggest you educate your community and make sure that RM responsibility can be shared. In fact, if you're the only one who *understands* how releases are done in Royal -- I don't think that Royal qualifies as a very healthy community, frankly. Thanks, Roman.
