My +1 I suggest taking the approach suggested by Gary to update the release notes in the SVN distribution directory to include the missing ticket for the user guide, and regenerate the site with the correct changes report and release notes.
I changed the open tickets to update the fix version for the next release. Alex On Mon, 31 Oct 2022 at 12:52, Gilles Sadowski <gillese...@gmail.com> wrote: > > > > [...] > > > Only the release notes and changes will be missing this. > > > > > > What is the precedent for changing the release notes after a vote? > > > Does this require an RC2? > > > > > > > We vote on specific sources: the commit hash identified by a git commit (a > > git tag) and the source zip/tar files; git and zip/tars must match. Jars > > and bin zip/tar files are only delivered as a convenience to our users. > > > > So, if you plan on changing the release note file that is inside the source > > zip and tar files, then that requires a new RC and vote. > > > > OTOH, you could just change the RN file on the dist area and in git after > > the release, and regenerate the site then if needed. > > > > It all depends on how tidy and accurate you want the release note to be. > > > > I like "tidy", but not to the point of forcing a new RC just for having > the release notes record the addition of a user guide... > > I'm fine voting +1. > > Regards, > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
