Mailing List Archive: Lucene: Java-Dev

Lucene 3.0.0 RC1

Index | Next | Previous | View Threaded

uwe at thetaphi

Nov 15, 2009, 1:34 PM

Post #1 of 5 (430 views)
Permalink

Lucene 3.0.0 RC1

Hallo Committers,

I want to start the release process tomorrow. The question:

Mark Miller created the branch after the release of 2.9.0, but the release
TODO says, that I should create the branch before the first RC. Robert also
wanted this today, because it would allow us to work for 3.1, while the
release process of 3.0 is running (but please no heavy commits like touching
all tests for junit4, it makes merging bugfixes to 3.0 and 2.9 harder).

So I would branch 3.0 tomorrow, so bug fixes in the RC must be also done on
the branch. I will also change the version numbers in trunk (3.1-dev) and
create a new trunk-BW-branch (30_bw_tests, also remove the Java 1.4 switch
for compiling BW branch).

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe [at] thetaphi

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

markrmiller at gmail

Nov 15, 2009, 1:42 PM

Post #2 of 5 (410 views)
Permalink

Re: Lucene 3.0.0 RC1 [In reply to]

The reason I created the branch at the last minute was because the 2.9
release was so large. Having to commit the release check/fix flurry of
activity against trunk and a branch would have been quite a pain. The
hope was also to keep devs on making the release right, rather than
continue with trunk dev. I don't think we have the same concern with 3.0
though. You can really do whatever makes sense with consensus - I waited
to create the branch because I brought up the concern on the list and
got agreement without any disagreement. It was a one time discussion for
2.9 though - I wouldn't feel bound by anything that happened during the
2.9 release for 3.0.

- Mark

Uwe Schindler wrote:
> Hallo Committers,
>
> I want to start the release process tomorrow. The question:
>
> Mark Miller created the branch after the release of 2.9.0, but the release
> TODO says, that I should create the branch before the first RC. Robert also
> wanted this today, because it would allow us to work for 3.1, while the
> release process of 3.0 is running (but please no heavy commits like touching
> all tests for junit4, it makes merging bugfixes to 3.0 and 2.9 harder).
>
> So I would branch 3.0 tomorrow, so bug fixes in the RC must be also done on
> the branch. I will also change the version numbers in trunk (3.1-dev) and
> create a new trunk-BW-branch (30_bw_tests, also remove the Java 1.4 switch
> for compiling BW branch).
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe [at] thetaphi
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
> For additional commands, e-mail: java-dev-help [at] lucene
>
>

--
- Mark

http://www.lucidimagination.com

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

buschmic at gmail

Nov 15, 2009, 2:36 PM

Post #3 of 5 (410 views)
Permalink

Re: Lucene 3.0.0 RC1 [In reply to]

I think it's okay to create a branch now and agree on a code freeze
(except severe bugs or doc patches) on the branch once the first RC is out.

And yes, discouraging big commits on trunk during the freeze is always a
good idea.

Michael

On 11/15/09 1:42 PM, Mark Miller wrote:
> The reason I created the branch at the last minute was because the 2.9
> release was so large. Having to commit the release check/fix flurry of
> activity against trunk and a branch would have been quite a pain. The
> hope was also to keep devs on making the release right, rather than
> continue with trunk dev. I don't think we have the same concern with 3.0
> though. You can really do whatever makes sense with consensus - I waited
> to create the branch because I brought up the concern on the list and
> got agreement without any disagreement. It was a one time discussion for
> 2.9 though - I wouldn't feel bound by anything that happened during the
> 2.9 release for 3.0.
>
> - Mark
>
> Uwe Schindler wrote:
>
>> Hallo Committers,
>>
>> I want to start the release process tomorrow. The question:
>>
>> Mark Miller created the branch after the release of 2.9.0, but the release
>> TODO says, that I should create the branch before the first RC. Robert also
>> wanted this today, because it would allow us to work for 3.1, while the
>> release process of 3.0 is running (but please no heavy commits like touching
>> all tests for junit4, it makes merging bugfixes to 3.0 and 2.9 harder).
>>
>> So I would branch 3.0 tomorrow, so bug fixes in the RC must be also done on
>> the branch. I will also change the version numbers in trunk (3.1-dev) and
>> create a new trunk-BW-branch (30_bw_tests, also remove the Java 1.4 switch
>> for compiling BW branch).
>>
>> Uwe
>>
>> -----
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: uwe [at] thetaphi
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
>> For additional commands, e-mail: java-dev-help [at] lucene
>>
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

lucene at mikemccandless

Nov 15, 2009, 3:13 PM

Post #4 of 5 (411 views)
Permalink

Re: Lucene 3.0.0 RC1 [In reply to]

+1 to create the branch now.

Mike

On Sun, Nov 15, 2009 at 4:34 PM, Uwe Schindler <uwe [at] thetaphi> wrote:
> Hallo Committers,
>
> I want to start the release process tomorrow. The question:
>
> Mark Miller created the branch after the release of 2.9.0, but the release
> TODO says, that I should create the branch before the first RC. Robert also
> wanted this today, because it would allow us to work for 3.1, while the
> release process of 3.0 is running (but please no heavy commits like touching
> all tests for junit4, it makes merging bugfixes to 3.0 and 2.9 harder).
>
> So I would branch 3.0 tomorrow, so bug fixes in the RC must be also done on
> the branch. I will also change the version numbers in trunk (3.1-dev) and
> create a new trunk-BW-branch (30_bw_tests, also remove the Java 1.4 switch
> for compiling BW branch).
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe [at] thetaphi
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
> For additional commands, e-mail: java-dev-help [at] lucene
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

rcmuir at gmail

Nov 15, 2009, 3:28 PM

Post #5 of 5 (407 views)
Permalink

Re: Lucene 3.0.0 RC1 [In reply to]

fyi, one reason I tossed the idea at Uwe was that its currently difficult
for me to even develop patches for new functionality/3.1 (ex. there is no
Version.LUCENE_31 constant yet)

i saw this the other day working on LUCENE-2067... no worries i do not want
to any do heavy committing

On Sun, Nov 15, 2009 at 6:13 PM, Michael McCandless <
lucene [at] mikemccandless> wrote:

> +1 to create the branch now.
>
> Mike
>
> On Sun, Nov 15, 2009 at 4:34 PM, Uwe Schindler <uwe [at] thetaphi> wrote:
> > Hallo Committers,
> >
> > I want to start the release process tomorrow. The question:
> >
> > Mark Miller created the branch after the release of 2.9.0, but the
> release
> > TODO says, that I should create the branch before the first RC. Robert
> also
> > wanted this today, because it would allow us to work for 3.1, while the
> > release process of 3.0 is running (but please no heavy commits like
> touching
> > all tests for junit4, it makes merging bugfixes to 3.0 and 2.9 harder).
> >
> > So I would branch 3.0 tomorrow, so bug fixes in the RC must be also done
> on
> > the branch. I will also change the version numbers in trunk (3.1-dev) and
> > create a new trunk-BW-branch (30_bw_tests, also remove the Java 1.4
> switch
> > for compiling BW branch).
> >
> > Uwe
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: uwe [at] thetaphi
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
> > For additional commands, e-mail: java-dev-help [at] lucene
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
> For additional commands, e-mail: java-dev-help [at] lucene
>
>

--
Robert Muir
rcmuir [at] gmail

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads