On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg <daniel.l.sahlb...@gmail.com>
wrote:
> This commit doesn't look correct.
>
> I executed the generate-upcoming-changes-log.sh manually yesterday and it
> created r1899244, removing a lot of log entries belonging to 1.14.1. This
> commit (which was executed by cron) restores them.
>
> The crontab entry is:
> [[[
> # Puppet Name: Update our upcoming changes list
> SVN=svn
> 15 4 * * * chronic ~/src/svn/site/tools/generate-upcoming-changes-log.sh
> ]]]
>
> The script begins with a comment
> [[[
> # This should be run from the root of a branches/1.{9,10,11}.x working
> copy.
> ]]]
>
> I suppose the crontab command should be changed to:
> cd ~/src/svn/1.14.x && chronic
> ~/src/svn/site/tools/generate-upcoming-changes-log.sh
>
> However that will create an "upcoming" only for 1.14 and not for 1.10. Any
> thoughts
>
We don't really have a place on the release notes page for "upcoming" for
two different major lines. For now it probably makes sense to show it for
1.14.x only, but when 1.15 is released we'll have to decide whether to show
"upcoming" for just 1.15 or separately for 1.14 and 1.15.
Regarding things disappearing and reappearing, some time ago I noticed that
if an error occurs in the script, such as it can't reach the repo, then it
fails to generate any text but proceeds to commit unconditionally. I don't
remember if that was ever fixed.
Nathan
