[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1835191 - /subversion/site/publish/docs/community-guide/releasing.part.html

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 6 Jul 2018 18:04:12 +0000

luke1410_at_apache.org wrote on Thu, Jul 05, 2018 at 21:13:37 -0000:
> +++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Jul 5 21:13:36 2018
> @@ -975,22 +975,19 @@ in the same directory as the tarballs.</
> +policy, we require testing and signatures from at least [one] PMC members on


> +The release manager is encouraged to wait at least 5 days for the signatures
> +before rolling the release to allow anybody (planning to) test(ing) the release
> +to complete signing the release before it's being rolled.</p>

s/roll/announce/g (including conjugations)

To "roll" a release means to create a tag and a tarball, which happens _before_
signatures are solicited. The RM actions after signatures have been collected
are to stage the release (`release.py move-to-dist`) and announce it (update
index.html and email announce@).



P.S. Since I'm already replying: I don't think giving the reader a choice
between "to allow anybody testing the release" and "to allow anybody planning
to test the release" is helpful. I suggest to pick one and drop the other :-)
Received on 2018-07-06 20:04:31 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.