Please vote for release candidate 1 for Solr 9.6.0
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/solr/solr-9.6.0-RC1-rev-f8e5a93c11267e13b7b43005a428bfb910ac6e57
You can run the smoke tester directly with this command:
python3 -u dev-tools/scripts/smokeTestRelease.
Initial release notes have been drafted here, please flesh out, refine,
copy edit as needed.
https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote9_6_0
-Gus
--
http://www.needhamsoftware.com (work)
https://a.co/d/b2sZLD9 (my fantasy fiction book)
NOTICE:
Branch branch_9_6 was cut a week ago, with agreement of an additional week
for further changes. That week has passed and we should now be in a
standard feature freeze. Versions updated to 9.7 on the stable branch.
Please observe the normal rules:
* No new features may be committed to the
LMK what you think of https://issues.apache.org/jira/browse/SOLR-17244
(more legible than the PR is my branch :
https://github.com/gus-asf/solr/blob/SOLR-17244/dev-docs/releasing.adoc)
On Mon, Apr 22, 2024 at 4:36 PM Jan Høydahl wrote:
> Hi,
>
> The error message is perhaps not too helpful for h
Hi,
The error message is perhaps not too helpful for how to proceed.
I believe you have initialized the wizard already for a bugfix release.
See $HOME/.solrrc if there is a version set already. Then it will complain
since it believes you are to release a bugfix from stable branch.
You can re-in
Here's links for everyone's meeting-related pages:
Confluence Meeting Notes:
https://cwiki.apache.org/confluence/display/SOLR/2024-04-29+Meeting+notes
TimeAndDate:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Solr+Community+Meetup%2C+April+2024&iso=20240429T09&p1=224&ah=1
Google Meet
Alright, I'm happy to volunteer for April.
Pending any more input on "when", let's shoot for Monday April 29th at
noon ET. The 29th gives us a full week between this decision and the
meeting. (I don't have strong opinions on that particular time-slot,
but we've used it for a number of recent mee
Welcome Jason :) and thanks again to David
On Mon, Apr 22, 2024 at 10:13 AM Jason Gerlowski
wrote:
> Thanks all for the kind words, and thanks especially to David for
> serving this past year!
>
> On Fri, Apr 19, 2024 at 9:00 AM Anshum Gupta
> wrote:
> >
> > Thank you for your effort, David!
>
The move to the latest is of course usually a good idea, but sometimes
beyond risk tolerance for some customers. If the fixes are already
committed and will be in future releases, a one-off custom build that is
effectively but not officially 9.1.2 might be worth considering. Don't give
it that numb
Thanks all for the kind words, and thanks especially to David for
serving this past year!
On Fri, Apr 19, 2024 at 9:00 AM Anshum Gupta wrote:
>
> Thank you for your effort, David!
>
> Congratulations, Jason!
>
> On Thu, Apr 18, 2024 at 7:47 PM David Smiley wrote:
>
> > The PMC has voted Jason Ge
Except it quit with an error complaining about the version before the
checkout step in the menus (or any menus)... so it does look at the local
checkout for that...
On Mon, Apr 22, 2024 at 9:11 AM Jan Høydahl wrote:
> You don't need to run the wizard from a pristine checkout, or even from
> the
You don't need to run the wizard from a pristine checkout, or even from the
clone in .solr-releases/
The only requirement is that you run the wizard from some recent enough
checkout of the correct branch.
The wizard will not use the "current" git repo for anything else than for
reading releaseWi
CHANGES for solrbot PRs is added during release by RM. You simply merge the PR.
Jan Høydahl
> 22. apr. 2024 kl. 12:58 skrev Eric Pugh :
>
> Ah.. So we don’t quite yet know how to deal with the aws and google
> libraries being constantly updated?
>
> It looks like SolrBot opened PR’s get the
Will definitely follow this release with some documentation of what you
just told and other basic "orientation". For example it refers to a "root"
folder but exactly what it intends for that folder is opaque until much
later in the process (place for code? place for artifacts? root of what?)
... y
Adding some discussions I had with @jan...@apache.org over
slack:
"Your client should be aware that they are vulnerable to a bunch of CVEs if
they stay on 9.1. See
https://solr.apache.org/security.html#cve-2023-50292-apache-solr-schema-designer-blindly-trusts-all-configsets-possibly-leading-to-rc
Ah.. So we don’t quite yet know how to deal with the aws and google libraries
being constantly updated?
It looks like SolrBot opened PR’s get the “dependency” label added. I looked
in Github PR’s,
https://github.com/apache/solr/pulls?page=2&q=is%3Apr+is%3Aopen+label%3Adependencies
and the
Hi all,
I managed to secure a sponsorship to work on a bug that impacted the
Learning To Rank module (re-scoring was ignoring query limits and time
allowed, causing outages and crashes).
The contribution has been merged already in 10, 9.x and 9.1:
https://issues.apache.org/jira/browse/SOLR-17018
I
Hi,
The wizard contains a step to create the NEXT version in Jira:
https://github.com/apache/solr/blob/main/dev-tools/scripts/releaseWizard.yaml#L662
I believe perhaps that instruction uses the x.y.0 pattern for minor releases.
If so, that is a wizard bug.
It also contains a Post-Release step
Hi Gus
Could be documentation is weak, but the assumption is that for a minor release
you run the wizard from branch_9x.
The wizard will not run commands unless you ask it to, but it will generate the
command, print it, and once you accept it will be run. If you prefer for som
reason to run a
19 matches
Mail list logo
