Re-reading I think I misunderstood. I thought somewhere it was said that
git repo was needed to build which I would consider important, but I guess
that was just re-building the src tarball itself that required it.

If the existing src tarball is sufficient to produce a working server based
solely on instructions in the README.md I have no further concerns.

On Mon, Nov 29, 2021 at 11:03 AM Dawid Weiss <dawid.we...@gmail.com> wrote:

> The basic build steps are included in the readme, Gus -
> https://github.com/apache/lucene/#building-with-gradle
>
> Is your comment about moving it to a separate file or about the
> instructions to build the package in general? If it's the latter then
> I think it's fine?
>
> Dawid
>
> On Mon, Nov 29, 2021 at 2:16 PM Gus Heck <gus.h...@gmail.com> wrote:
> >
> > Not suggesting it's a show stopper, just that this would be an easily
> found and consumed way to document the information revealed in this
> discussion.
> >
> > On Mon, Nov 29, 2021 at 8:13 AM Uwe Schindler <u...@thetaphi.de> wrote:
> >>
> >> Hi,
> >>
> >> The same applies for the historical time. It was never possible to do a
> full release with only the source tarball.
> >>
> >> The only thing that does not work is: assembleSourceRelease, because it
> requires "git archive" to build the src.tgz. But why should anybody do
> this? You have a src.tgz already why create another one from itsself?
> >>
> >> You can create a binary release without problems (at least that worked
> yesterday), it will just not have a git hash in the metadata of JAR files
> (and so on). But the version number is always "SNAPSHOT" unless you define
> your own (we do this to prevent "unauthorized artifacts created
> accidentally). If somebody wants to release a custom Lucene with patches,
> one can pass -Dversion.suffix="Ubuntu20.04-foobar" to make a customized
> release.
> >>
> >> Uwe
> >>
> >> -----
> >> Uwe Schindler
> >> Achterdiek 19, D-28357 Bremen
> >> https://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>
> >> > -----Original Message-----
> >> > From: Dawid Weiss <dawid.we...@gmail.com>
> >> > Sent: Monday, November 29, 2021 1:33 PM
> >> > To: Lucene Dev <dev@lucene.apache.org>
> >> > Subject: Re: [VOTE] Release Lucene 9.0.0 RC3
> >> >
> >> > I don't think it's a showstopper. This applies to any 9x branch -
> >> > perhaps starting from main. We can extract these instructions into a
> >> > separate document. On the other hand, it wouldn't be shown up there on
> >> > github front-page then... and times have changed - this is where most
> >> > folks would probably end up reading the instructions, not the source
> >> > bundle?
> >> >
> >> > D.
> >> >
> >> > On Mon, Nov 29, 2021 at 1:01 PM Gus Heck <gus.h...@gmail.com> wrote:
> >> > >
> >> > > Seems to me the details for how to turn a src tarball into
> something that can
> >> > be compiled should go in a BUILDING.txt file?
> >> > >
> >> > > On Mon, Nov 29, 2021 at 3:00 AM Dawid Weiss <dawid.we...@gmail.com>
> >> > wrote:
> >> > >>
> >> > >> SUCCESS! [0:17:23.949074]
> >> > >>
> >> > >> +1.
> >> > >>
> >> > >> D.
> >> > >>
> >> > >> On Fri, Nov 26, 2021 at 3:31 PM Adrien Grand <jpou...@gmail.com>
> wrote:
> >> > >> >
> >> > >> > Please vote for release candidate 3 for Lucene 9.0.0.
> >> > >> >
> >> > >> > The artifacts can be downloaded from:
> >> > >> >
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.0.0-RC3-rev-
> >> > 1ddce848cf3d5067efcafc6569d5f8203e56af0b
> >> > >> >
> >> > >> > You can run the smoke tester directly with this command:
> >> > >> >
> >> > >> > python3 -u dev-tools/scripts/smokeTestRelease.py \
> >> > >> >
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.0.0-RC3-rev-
> >> > 1ddce848cf3d5067efcafc6569d5f8203e56af0b
> >> > >> >
> >> > >> > The vote will be open until 2021-11-30 9:00 UTC.
> >> > >> >
> >> > >> > [ ] +1  approve
> >> > >> > [ ] +0  no opinion
> >> > >> > [ ] -1  disapprove (and reason why)
> >> > >> >
> >> > >> > Here is my +1.
> >> > >> >
> >> > >> > --
> >> > >> > Adrien
> >> > >> >
> >> > >> >
> ---------------------------------------------------------------------
> >> > >> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> > >> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >> > >> >
> >> > >>
> >> > >>
> ---------------------------------------------------------------------
> >> > >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> > >> For additional commands, e-mail: dev-h...@lucene.apache.org
> >> > >>
> >> > >
> >> > >
> >> > > --
> >> > > http://www.needhamsoftware.com (work)
> >> > > http://www.the111shift.com (play)
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >
> >
> > --
> > http://www.needhamsoftware.com (work)
> > http://www.the111shift.com (play)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)

Reply via email to