subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf <...@daniel.shahaf.name>
Subject Re: svn commit: r1835191 - /subversion/site/publish/docs/community-guide/releasing.part.html
Date Fri, 06 Jul 2018 18:04:12 GMT
luke1410@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

s/members/member/

> +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@).

Cheers,

Daniel

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 :-)

Mime
View raw message