Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Lucene: Java-Dev

Release Lucene Java 2.9.2 & 3.0.(1|2) together soon

 

 

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded


uwe at thetaphi

Feb 7, 2010, 5:29 AM

Post #1 of 4 (620 views)
Permalink
Release Lucene Java 2.9.2 & 3.0.(1|2) together soon

Hallo all,

I think it is ready to start the release process of 3.0.(1|2) and 2.9.2 soon. Before building the artifacts I would compare the changelogs and try to merge them to get a similar bugfix level for both versions. I would like to release both versions on the same day with the same release message. I have all scripts available here and can start the builds easily on my solaris box.

Maybe we should name the next 3.0 release 3.0.2 (and not use .1?) - so it says 2.9.2 and 3.0.2 are equal from the bugfix level?

Hopefully these will be the last releases from these branches and we can release 3.1 after flex is in.

Uwe

P.S.: Robert: And I will explicitly try out the demo application :-)
-----
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


lucene at mikemccandless

Feb 7, 2010, 5:45 AM

Post #2 of 4 (588 views)
Permalink
Re: Release Lucene Java 2.9.2 & 3.0.(1|2) together soon [In reply to]

+1 to release. Thank you for volunteering :) We've got a number of
good bug fixes pending...

But: I think we should simply name it 3.0.1? If we skip 3.0.1 I think
it will cause confusion? We can state in the CHANGES that 2.9.2 has
same bug fixes as 3.0.1 and vice/versa?

Mike

On Sun, Feb 7, 2010 at 8:29 AM, Uwe Schindler <uwe [at] thetaphi> wrote:
> Hallo all,
>
> I think it is ready to start the release process of 3.0.(1|2) and 2.9.2 soon. Before building the artifacts I would compare the changelogs and try to merge them to get a similar bugfix level for both versions. I would like to release both versions on the same day with the same release message. I have all scripts available here and can start the builds easily on my solaris box.
>
> Maybe we should name the next 3.0 release 3.0.2 (and not use .1?) - so it says 2.9.2 and 3.0.2 are equal from the bugfix level?
>
> Hopefully these will be the last releases from these branches and we can release 3.1 after flex is in.
>
> Uwe
>
> P.S.: Robert: And I will explicitly try out the demo application :-)
> -----
> 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


simon.willnauer at googlemail

Feb 7, 2010, 6:00 AM

Post #3 of 4 (582 views)
Permalink
Re: Release Lucene Java 2.9.2 & 3.0.(1|2) together soon [In reply to]

On Sun, Feb 7, 2010 at 2:45 PM, Michael McCandless
<lucene [at] mikemccandless> wrote:
> +1 to release.  Thank you for volunteering :)  We've got a number of
> good bug fixes pending...
+1 I already know a couple of people looking forward to this releases!
>
> But: I think we should simply name it 3.0.1?  If we skip 3.0.1 I think
> it will cause confusion?  We can state in the CHANGES that 2.9.2 has
> same bug fixes as 3.0.1 and vice/versa?
We should not skip 3.0.1! I agree with mike there is no need for
skipping it and it will cause lots of confusion I guess.

simon
>
> Mike
>
> On Sun, Feb 7, 2010 at 8:29 AM, Uwe Schindler <uwe [at] thetaphi> wrote:
>> Hallo all,
>>
>> I think it is ready to start the release process of 3.0.(1|2) and 2.9.2 soon. Before building the artifacts I would compare the changelogs and try to merge them to get a similar bugfix level for both versions. I would like to release both versions on the same day with the same release message. I have all scripts available here and can start the builds easily on my solaris box.
>>
>> Maybe we should name the next 3.0 release 3.0.2 (and not use .1?) - so it says 2.9.2 and 3.0.2 are equal from the bugfix level?
>>
>> Hopefully these will be the last releases from these branches and we can release 3.1 after flex is in.
>>
>> Uwe
>>
>> P.S.: Robert: And I will explicitly try out the demo application :-)
>> -----
>> 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
>
>

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


gsingers at apache

Feb 9, 2010, 12:30 PM

Post #4 of 4 (505 views)
Permalink
Re: Release Lucene Java 2.9.2 & 3.0.(1|2) together soon [In reply to]

On Feb 7, 2010, at 8:45 AM, Michael McCandless wrote:

> +1 to release. Thank you for volunteering :) We've got a number of
> good bug fixes pending...
>
> But: I think we should simply name it 3.0.1? If we skip 3.0.1 I think

I'd agree. Stick w/ 3.0.1

-Grant

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

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.