Re: Bugfix release Lucene/Solr 8.11.3
Shouldn't we wait for the 9.4.1 to go out first? That's what I was holding out on. On Sat, 13 Jan, 2024, 12:43 am Houston Putman, wrote: > NOTICE: > > I am now preparing for a bugfix release from branch branch_8_11 > > Please observe the normal rules for committing to this branch: > > * Before committing to the branch, reply to this thread and argue > why the fix needs backporting and how long it will take. > * All issues accepted for backporting should be marked with 8.11.3 > in JIRA, and issues that should delay the release must be marked as > Blocker > * All patches that are intended for the branch should first be committed > to the unstable branch, merged into the stable branch, and then into > the current release branch. > * Only Jira issues with Fix version 8.11.3 and priority "Blocker" will > delay > a release candidate build. >
[VOTE] Release Solr 9.4.1 RC1
Please vote for release candidate 1 for Solr 9.4.1 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476 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.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476 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.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476/solr && \ docker build $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-full \ --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ -t solr-rc:9.4.1-1 && \ docker build $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-slim \ --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ -t solr-rc:9.4.1-1-slim The vote will be open for at least 72 hours i.e. until 2024-01-16 17:00 UTC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here is my +1 ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley
Re: [VOTE] Release Solr 9.4.1 RC1
+1 (binding) SUCCESS! [0:42:51.792486] Also built docker container and spun up the server locally. PS: Need to remove extra newline between the two lines of command when copy/pasting: python3 -u dev-tools/scripts/smokeTestRelease.py \ https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476 Jan > 13. jan. 2024 kl. 17:14 skrev David Smiley : > > Please vote for release candidate 1 for Solr 9.4.1 > > The artifacts can be downloaded from: > > https://dist.apache.org/repos/dist/dev/solr/solr-9.4.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476 > > > 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.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476 > > > 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.1-RC1-rev-57762a5b52a9d40a6f15441c4adeb76f0b045476/solr > && \ > > docker build $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-full \ > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ > >-t solr-rc:9.4.1-1 && \ > > docker build $SOLR_DOWNLOAD_SERVER/9.4.1/docker/Dockerfile.official-slim \ > >--build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \ > >-t solr-rc:9.4.1-1-slim > > > The vote will be open for at least 72 hours i.e. until 2024-01-16 17:00 UTC. > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > Here is my +1 > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley - To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
[DISCUSS] SIP-20: Separation of Compute and Storage in SolrCloud
I have created SIP-20 https://cwiki.apache.org/confluence/display/SOLR/SIP-20%3A+Separation+of+Compute+and+Storage+in+SolrCloud In the next few days I will create a Jira + a branch that implements the SIP proposal and that includes documentation on how to approach that branch and what's in it. This proposed contribution is based on work done at Salesforce these last few years and currently running at scale in multiple regions. Thanks, Ilan - To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
Re: Build: checkWorkingCopyClean -- is there value?
https://github.com/apache/solr/pull/2196 ~ David On Wed, Sep 6, 2023 at 11:17 PM David Smiley wrote: > Honestly, I would prefer to do away with it entirely. Dubious logic that > has been made to only output a warning will continue to be a part of the > code weight of our sprawling build. It will need to be maintained[1]. It > needs to do it's calculations on every check/precommit. I don't even want > to be "warned" about the fact that I am modifying files. *Of course* > there are modified files; I am actually work on this codebase! > > [1] even making it have a computed default is an example of this > maintenance cost! > > ~ David > > > On Wed, Sep 6, 2023 at 8:46 PM Michael Gibney > wrote: > >> Something like this could work?: >> >> >> https://github.com/apache/solr/blob/eaaabbfa33456639613a7a6aecc37cd2d89e5dfa/gradle/globals.gradle#L168-L171 >> >> On Wed, Sep 6, 2023 at 5:26 PM David Smiley >> wrote: >> > >> > Is there a property or something used to detect that the build is being >> run >> > in a CI or CI-like env? >> > ~ David >> > >> > >> > On Wed, Sep 6, 2023 at 4:50 PM Shawn Heisey >> wrote: >> > >> > > On 9/6/23 13:21, Uwe Schindler wrote: >> > > > The idea is that jenkins runs it after the builds to figure out if >> > > > something changed in the working copy. At ANT times this was >> implemented >> > > > exactly like this, we failed build on Jenkins when the working copy >> > > > changed. This was especially important before we used >> SecurityManager to >> > > > prevent tests writing outside their temporary dirs. We had tests >> > > > touching files in working copy. >> > > >> > > That makes sense, and for Jenkins it sounds like a very good idea. I >> > > think that Jenkins should probably explicitly request that check ... >> > > having it enabled by default for everyone is not the best idea IMHO. >> > > >> > > Thanks, >> > > Shawn >> > > >> > > >> > > - >> > > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org >> > > For additional commands, e-mail: dev-h...@solr.apache.org >> > > >> > > >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org >> For additional commands, e-mail: dev-h...@solr.apache.org >> >>
Re: [DISCUSS] SIP-20: Separation of Compute and Storage in SolrCloud
+1, thanks for the contribution Ilan! Looking forward to seeing this coming to fruition. On Sun, 14 Jan 2024 at 03:40, Ilan Ginzburg wrote: > I have created SIP-20 > > https://cwiki.apache.org/confluence/display/SOLR/SIP-20%3A+Separation+of+Compute+and+Storage+in+SolrCloud > > In the next few days I will create a Jira + a branch that implements > the SIP proposal and that includes documentation on how to approach > that branch and what's in it. > > This proposed contribution is based on work done at Salesforce these > last few years and currently running at scale in multiple regions. > > Thanks, > Ilan > > - > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
