Nathan Hartman wrote on Fri, 09 Jul 2021 00:55 +00:00:
> On Thu, Jul 8, 2021 at 5:13 PM Daniel Sahlberg
> <daniel.l.sahlb...@gmail.com> wrote:
> > Den tis 6 juli 2021 kl 04:25 skrev Nathan Hartman
> > <hartman.nat...@gmail.com>:
> >> On Mon, Jul 5, 2021 at 9:27 PM Daniel Shahaf <d...@daniel.shahaf.name>
> >> wrote:
> >>> Daniel Sahlberg wrote on Sat, Jul 03, 2021 at 23:45:01 +0200:
> >>> > It seems that the API and JavaHL docs for 1.13 and 1.14 are missing. I
> >>> > have
> >>> > generated them from the branches.
> >>>
> >>> Are there any relevant differences between the branches (@HEAD) and the
> >>> latest tags on each branch?
> >> Oh, they probably should have been generated from the latest tags, not the
> >> branches.
> >
> > Oh, [invective], my bad!
>
>
> Nah, you did what's documented in HACKING. Is that a "bug" in HACKING?
Generating the site API docs from _any_ revision of branches/1.A.x
(whether @HEAD, @${MAGIC_REVISION}, or anything else) would mean
SVN_VER_TAG and SVN_VER_REVISION would have wrong values in the
generated API docs. So, if HACKING says to generate a release's docs
from branches/1.A.x, that's a bug.
Also, HACKING doesn't define the term "magic revision" (= the revision
that's tagged, visible as the copyfrom of the tag in the repository and
the value of SVN_VER_REVISION in the tag's source tree). The term is used in
https://subversion.apache.org/docs/community-guide/how-to-roll-releases-in-private.txt,
though.
