Re: [ALL] Valid reasons for blocking a release?

I don't think a valid site or the odd missing file is enough to cancel a release - but if there are multiple such issues it should also be taken into consideration. Even the odd -1 vote can be ignored if there are enough positive votes. On 15 September 2016 at 12:42, Stefan Bodewig

Re: [ALL] Valid reasons for blocking a release?

On 2016-09-16, Gilles wrote: > Is the site a valid reason? to cancel a release? IMHO no. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Re: [ALL] Valid reasons for blocking a release?

On Thu, 15 Sep 2016 09:20:14 -0700, Gary Gregory wrote: On Thu, Sep 15, 2016 at 4:02 AM, Gilles wrote: On Wed, 14 Sep 2016 07:41:01 -0700, Gary Gregory wrote: "I'd rather not redo the release steps just for files that are meaningful only when browsing the code

Re: [ALL] Valid reasons for blocking a release? (Was: [REMINDER][VOTE][RC1] Release Commons Rng 1.0)

On Thu, Sep 15, 2016 at 4:02 AM, Gilles wrote: > On Wed, 14 Sep 2016 07:41:01 -0700, Gary Gregory wrote: > >> "I'd rather not redo the release steps just for files that are >> meaningful only when browsing the code repository mirror at >> Github." >> >> I know our

Re: [ALL] Valid reasons for blocking a release?

On 2016-09-15, Gilles wrote: > On Wed, 14 Sep 2016 07:41:01 -0700, Gary Gregory wrote: >> "I'd rather not redo the release steps just for files that are >> meaningful only when browsing the code repository mirror at >> Github." >> I know our release process is a pain, so maybe we should see if

[ALL] Valid reasons for blocking a release? (Was: [REMINDER][VOTE][RC1] Release Commons Rng 1.0)

On Wed, 14 Sep 2016 07:41:01 -0700, Gary Gregory wrote: "I'd rather not redo the release steps just for files that are meaningful only when browsing the code repository mirror at Github." I know our release process is a pain, so maybe we should see if we can improve it. This needs a separate