Definitely a good thing to add to the docs. Thanks Gus!
On Sun, Apr 28, 2024 at 1:24 PM Gus Heck wrote:
>
> Ok it seems to be resolved now. I think I'll document this (and some other
> high level info) in the releasing doc I've been working on in SOLR-17244 so
> future release managers don't pan
Ok it seems to be resolved now. I think I'll document this (and some other
high level info) in the releasing doc I've been working on in SOLR-17244 so
future release managers don't panic prematurely. Thx for the clarification.
On Sun, Apr 28, 2024 at 11:00 AM Gus Heck wrote:
> Hmm if it's this:
Hmm if it's this:
https://ci-builds.apache.org/job/Solr/job/solr-reference-guide-official/
it's due soon.
On Sun, Apr 28, 2024 at 10:58 AM Gus Heck wrote:
> Is this done by a jenkins job, (or part of one)? Where can I figure out
> the schedule? I tried looking at http last-modified headers, but
Is this done by a jenkins job, (or part of one)? Where can I figure out the
schedule? I tried looking at http last-modified headers, but those are all
over the map and I suspect (guess) those dates may relate to when it was
cached by a caching layer, not when it was built (headers indicate there's
The ref guide gets built nightly by a jenkins job. Either the job isnt
working or we just need to wait till the next build.
“Beta” is used when the release branch exists but the release wizard step
of updating the antora.yaml (after the release is done) has not been done
(or is waiting on the nigh
I was about to send announcement emails for 9.6 but then I discovered that
somehow the ref guide didn't seem to get the right version, and isn't quite
working... It lists a 9.6-beta version, which I had noted this 9.6-beta at
one point but I assumed that since I had never typed the word "beta"
anyw
