Whoever created the JIRA "release" named "9.6.0" (and 9.5.0 for that
matter) made a small mistake; it should have been 9.6 (and 9.5) based
on past conventions. You should simply re-assign the existing issues
using 9.6 (there are only 2), *delete* that one, then *rename* "9.6.0"
to "9.6". And rena
It seems in the last couple of point releases we've tagged stuff as 9.4 and
9.5 in Jira, but this time around 9.6.0 has been used in 59 out of 61
issues...
I'm guessing, we want to bulk change all of that to 9.6 to match prior
releases...
LMK if this doesn't sound right, or I missed the memo on a
Also I just realized that despite --dry-run it seems to have written a
.solrrc file in my home dir (it did not write it in ~/.solr-releases that
it suggested as a root?)
it seems unexpected for --dry-run to leave persistent changes?
On Sun, Apr 21, 2024 at 3:37 PM Gus Heck wrote:
> I had initia
I had initiated dry runs a few times earlier this week and it stopped on
various dependencies, and I've not got those checks happy, but now I'm
getting:
"You can only release bugfix releases from an existing release branch"
The logic I see in the code doesn't make any sense...
def validate_r
