Release was aborted and once I backport the jetty PR I will restart it.

On Tue, Oct 10, 2023 at 3:43 PM Tomás Fernández Löbbe <tomasflo...@gmail.com>
wrote:

> I agree, let's upgrade Jetty for 9.4
>
> On Tue, Oct 10, 2023 at 2:30 PM Alex Deparvu <stilla...@apache.org> wrote:
>
> > I think beyond this change, there is also a Jetty 10.0.17 security update
> > release [0] which would need close evaluation to determine if we should
> > include it in 9.4.0.
> >
> > best,
> > alex
> >
> > [0] https://github.com/eclipse/jetty.project/releases/tag/jetty-10.0.17
> >
> >
> >
> > On Tue, Oct 10, 2023 at 2:06 PM Jan Høydahl <jan....@cominvent.com>
> wrote:
> >
> > > Fix: https://github.com/apache/solr/pull/2000
> > >
> > > Feel free to argue why this bug should not warrant a re-spin.
> > >
> > > Jan
> > >
> > > > 10. okt. 2023 kl. 13:08 skrev Jan Høydahl <jan....@cominvent.com>:
> > > >
> > > > Smoke tester: SUCCESS! [0:47:58.342068]
> > > >
> > > > Manual testing:
> > > > Started Solr locally on my mac outputs three lines of error mesages
> > > about entropy:
> > > >
> > > >> *** [WARN] *** Your open file limit is currently 256.
> > > >>  It should be set to 65000 to avoid operational disruption.
> > > >>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS
> to
> > > false in your profile or solr.in.sh
> > > >> *** [WARN] ***  Your Max Processes Limit is currently 5333.
> > > >>  It should be set to 65000 to avoid operational disruption.
> > > >>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS
> to
> > > false in your profile or solr.in.sh
> > > >> cat: /proc/sys/kernel/random/entropy_avail: No such file or
> directory
> > > >> cat: /proc/sys/kernel/random/poolsize: No such file or directory
> > > >> Error: Either no entropy is available or the pool size is zero.
> > > >> Waiting up to 180 seconds to see Solr running on port 8983 [|]
> > > >> Started Solr server on port 8983 (pid=42390). Happy searching!
> > > >
> > > > This is introduced in SOLR-16644 <
> > > https://issues.apache.org/jira/browse/SOLR-16644>, and obviously
> assumes
> > > a Linux system.
> > > > It will be quite confusing for Mac users or users of other non-linux
> > > systems (AIX/FreeBSD?).
> > > > The entopy probing using /proc/ should only be attempted on linux,
> and
> > > probably skipped silently on other OSes.
> > > >
> > > > For this reason I'll vote -1
> > > >
> > > > Jan
> > > >
> > > >
> > > >> 5. okt. 2023 kl. 21:51 skrev Alex Deparvu <stilla...@apache.org>:
> > > >>
> > > >> Please vote for release candidate 1 for Solr 9.4.0
> > > >>
> > > >> The artifacts can be downloaded from:
> > > >>
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.0-RC1-rev-ee474b7db483c2242ce1d75074258236ca22103b
> > > >>
> > > >> You can run the smoke tester directly with this command:
> > > >>
> > > >> python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > >>
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.0-RC1-rev-ee474b7db483c2242ce1d75074258236ca22103b
> > > >>
> > > >> You can build a release-candidate of the official docker images
> (full
> > &
> > > >> slim) using the following command:
> > > >>
> > > >> SOLR_DOWNLOAD_SERVER=
> > > >>
> > >
> >
> https://dist.apache.org/repos/dist/dev/solr/solr-9.4.0-RC1-rev-ee474b7db483c2242ce1d75074258236ca22103b/solr
> > > >> && \
> > > >>  docker build
> > > $SOLR_DOWNLOAD_SERVER/9.4.0/docker/Dockerfile.official-full \
> > > >>    --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >>    -t solr-rc:9.4.0-1 && \
> > > >>  docker build
> > > $SOLR_DOWNLOAD_SERVER/9.4.0/docker/Dockerfile.official-slim \
> > > >>    --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >>    -t solr-rc:9.4.0-1-slim
> > > >>
> > > >> The vote will be open for at least 72 hours i.e. until 2023-10-08
> > 20:00
> > > UTC.
> > > >>
> > > >> [ ] +1  approve
> > > >> [ ] +0  no opinion
> > > >> [ ] -1  disapprove (and reason why)
> > > >>
> > > >> Here is my +1 (which I am not completely sure, but I think it is
> > > >> non-binding)
> > > >>
> > > >> best,
> > > >> alex
> > > >
> > >
> > >
> >
>

Reply via email to