Re: Maintenance of Solr's official Dockerfile

There's still a lot of questions up in the air, and it's going to take some time to make the necessary decisions/changes. This shouldn't affect the 8.5 release. On Wed, Feb 26, 2020 at 6:08 AM Alan Woodward wrote: > Is the release of the docker image going to be part of the standard > Lucene/Sol

Re: Maintenance of Solr's official Dockerfile

Is the release of the docker image going to be part of the standard Lucene/Solr release process? I ask because I’m planning on starting an 8.5 release next week, and I know nothing about Docker images... > On 25 Feb 2020, at 16:04, David Smiley wrote: > > I wonder what official information ASF

Re: Maintenance of Solr's official Dockerfile

I wonder what official information ASF provides on this matter. I did some searching and found this page: https://cwiki.apache.org/confluence/display/INCUBATOR/DistributionGuidelines. (see "Docker" heading) which was nicely short and to the point but doesn't seem to answer. "DRAFT" 4 times is at

Re: Maintenance of Solr's official Dockerfile

I think se are not technically re-releasing Solr 8.4 even if that official docker image gets re-built with latest versions of Ubuntu and JRE11 when re release e.g. 8.5. The Apache Solr/Lucene binaries are still the exact same bits, we just change the base image — equivalent to upgrading Linux a

Re: Maintenance of Solr's official Dockerfile

I have a separate question about the release process. As I currently understand it, whenever docker-solr is released, every version in its configs is rebuilt and re-released. This means that v

Re: Maintenance of Solr's official Dockerfile

I propose we continue to work with the existing docker-solr repo for some time still, until we fully understand how we want to proceed with moving to ASF owned git infra and hub accounts. I feel that some work should have higher priority for now: - Document running Solr on Docker in Ref Guide -

Re: Maintenance of Solr's official Dockerfile

> Yes, it should be easy to build a docker image «from source», or at least as a gradle build task. That could piggy-back on the distro tgz file which should make it not too different - we just pull the release from local disk instead of from the mirrors. We do this at Salesforce in our local Luce

Re: Maintenance of Solr's official Dockerfile

>> 1. Are we allowed to maintain ASF code in a non-ASF repo? If not, how do we >> transition to >> an ASF git repo? >> * Can it be a sub folder in our main repo or does it need to be a >> separate repo? > > The way it works (from the official library’s point of view), is that we > maintain

Re: Maintenance of Solr's official Dockerfile

[pardon me breaking the email threading here; only just joined] Jan wrote: > Next step would be to agree on how we bring the current code into our project > and ASF repos > in the best possible way. Questions that arise are: > > 1. Are we allowed to maintain ASF code in a non-ASF repo? If not,

Re: Maintenance of Solr's official Dockerfile

Hi Jan, Thanks or the update, and thanks Jan from Martijn for the donation! :) I think that regardless of what the community decides to do with the docker-solr repo, a good first step would be to add a Docker folder to the Apache repository that contains a base Dockerfile and a README. In that RE

Maintenance of Solr's official Dockerfile

Hi, The Lucene project is asked to take over maintenance of the official Solr Dockerfile that ends up on Docker hub (located in https://github.com/docker-solr/docker-solr ). We have received a Software Grant from current maintainer Martijn Koster who