On Sat 9 Jun 2018 at 08:48, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> just for sake of process, but this is IMHO where the current process is > heavy: I said it before, and i’ll Say it again... my intention with idea of seconding was only for the 3.5.0 release and not as an ongoing process (with the possible exception of once an “intent to release” as been declared) Now granted I have declared an intent to release, and we have had issues getting the build stable... but from my POV outside of a release burn down, as long as CI is passing, we shouldn’t bother with seconds... Now once someone steps up as a release manager and says “i’m Going to cut a release”, then the priority should be ensuring the release can be cut, and in that case I think looking for seconding before merge is reasonable... but the rest of the time is just IMO a habit we picked up from the circumstances of the “big revert”... if big reverts become a habit, then yes... but we’ve had one in what 14+ years?... seconding all the time seems silly to me just because we once had to do a big revert > > > seconders for MNG-6364 Enhanced Jenkinsfile to test Core with JDK 9 ? > > > https://github.com/apache/maven/commit/34af3f9f96b8062a0146d99a2f200717896f9eaa +1 <https://github.com/apache/maven/commit/34af3f9f96b8062a0146d99a2f200717896f9eaa> > > Regards, > > Hervé > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
