On 21 September 2014 11:58, Oleg Kalnichevski <[email protected]> wrote: > On Sun, 2014-09-21 at 11:54 +0100, sebb wrote: >> On 21 September 2014 11:22, Oleg Kalnichevski <[email protected]> wrote: >> > On Sun, 2014-09-21 at 00:52 +0100, sebb wrote: >> >> On 20 September 2014 13:49, Oleg Kalnichevski <[email protected]> wrote: >> >> > On Sat, 2014-09-20 at 08:37 -0400, Gary Gregory wrote: >> >> >> I do not understand why there is not a link to a pre-built site for >> >> >> this RC. >> >> >> >> >> > >> >> > Website is not a release artifact and is not a part of the release >> >> > process. >> >> >> >> No, but the RM is expected to run at least the RAT and Clirr reports, >> >> and include them in the vote e-mail to show that these have been done. >> >> >> > >> > mvn clirr:check apache-rat:check >> >> That does not show the output. >> > > It performs necessary validation.
I meant that showing the command needed to check the release does not document that it has been run as part of the release checking, nor does it document the result of running the check. >> >> Also the review can check if there are any obvious errors in the site >> >> so these can be fixed before deployment. >> > >> > This is precisely the kind of madness I am trying to avoid. Website >> > deployment and release votes are completely unrelated. >> >> They _are_ related because the website has to be updated to publish >> the new release. >> And the website has to agree with the currently supported release(s). >> > > Which has nothing to do with the release vote. > > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
