You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Doug Cutting <cu...@lucene.com> on 2003/10/21 20:52:28 UTC
1.3 RC2
Should I go ahead and make this release, or should we wait for a fix to
the timestamp problem? I'm leaving town Thursday, and can either make
this release tomorrow morning, or not until November. My hunch is to go
ahead and make an RC release tomorrow, then, in November, when the
timestamp problem is resolved, make a 1.3 final release. Does that
sound like a good plan?
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Scott Ganyo <sc...@etapestry.com>.
+1
Doug Cutting wrote:
> Should I go ahead and make this release, or should we wait for a fix
> to the timestamp problem? I'm leaving town Thursday, and can either
> make this release tomorrow morning, or not until November. My hunch
> is to go ahead and make an RC release tomorrow, then, in November,
> when the timestamp problem is resolved, make a 1.3 final release.
> Does that sound like a good plan?
>
> Doug
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
--
...there is nothing more difficult to execute, nor more dubious of success, nor more dangerous to administer than to introduce a new order to things; for he who introduces it has all those who profit from the old order as his enemies; and he has only lukewarm allies in all those who might profit from the new. - Niccolo Machiavelli
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Dmitry Serebrennikov <dm...@earthlink.net>.
+1
Doug, I didn't have a chance to apply your patches and test them yet.
From just a quick review, it looks like everything should be fine. Now
that the changes are in CVS, I can more easily check them out. But if
the tests pass, I'm not worried. :)
Dmitry.
Doug Cutting wrote:
> Should I go ahead and make this release, or should we wait for a fix
> to the timestamp problem? I'm leaving town Thursday, and can either
> make this release tomorrow morning, or not until November. My hunch
> is to go ahead and make an RC release tomorrow, then, in November,
> when the timestamp problem is resolved, make a 1.3 final release.
> Does that sound like a good plan?
>
> Doug
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Otis Gospodnetic <ot...@yahoo.com>.
I guess I should have given my opinion in my +1 email.
I think we can live without the timestamp patch for now. This would be
a RC release after all, not a real release. Like Doug already said,
the timestamp patch can be added after RC2 and before 1.3 final.
Otis
--- Doug Cutting <cu...@lucene.com> wrote:
> Hani Suleiman wrote:
> > Mmm, while a release would be nice, I think the timestamp thing is
> a
> > significant enough change that it'd be good to have it in an RC
> release
> > before final.
>
> Perhaps. So the question today is: should we go ahead and do an RC
> tomorrow without a timestamp patch? (Unless someone submits a good
> timestamp patch before tomorrow...) We can still decide later to do
> another RC after the timestamp bug is patched, or not.
>
> Doug
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Hani Suleiman <ha...@formicary.net>.
alright alright, I thought that 1.3 final follows RC2, but I suppose
there's no legal reason why there can't be an RC 3 ;)
On Tuesday, October 21, 2003, at 07:13 PM, Erik Hatcher wrote:
> I vote to go for it as-is. Release early, release often.
>
> If there are issues with any released version, we can always make
> another release :)
>
> Erik
>
> On Tuesday, October 21, 2003, at 05:59 PM, Doug Cutting wrote:
>
>> Hani Suleiman wrote:
>>> Mmm, while a release would be nice, I think the timestamp thing is a
>>> significant enough change that it'd be good to have it in an RC
>>> release before final.
>>
>> Perhaps. So the question today is: should we go ahead and do an RC
>> tomorrow without a timestamp patch? (Unless someone submits a good
>> timestamp patch before tomorrow...) We can still decide later to do
>> another RC after the timestamp bug is patched, or not.
>>
>> Doug
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
I vote to go for it as-is. Release early, release often.
If there are issues with any released version, we can always make
another release :)
Erik
On Tuesday, October 21, 2003, at 05:59 PM, Doug Cutting wrote:
> Hani Suleiman wrote:
>> Mmm, while a release would be nice, I think the timestamp thing is a
>> significant enough change that it'd be good to have it in an RC
>> release before final.
>
> Perhaps. So the question today is: should we go ahead and do an RC
> tomorrow without a timestamp patch? (Unless someone submits a good
> timestamp patch before tomorrow...) We can still decide later to do
> another RC after the timestamp bug is patched, or not.
>
> Doug
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Doug Cutting <cu...@lucene.com>.
Hani Suleiman wrote:
> Mmm, while a release would be nice, I think the timestamp thing is a
> significant enough change that it'd be good to have it in an RC release
> before final.
Perhaps. So the question today is: should we go ahead and do an RC
tomorrow without a timestamp patch? (Unless someone submits a good
timestamp patch before tomorrow...) We can still decide later to do
another RC after the timestamp bug is patched, or not.
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Hani Suleiman <ha...@formicary.net>.
Mmm, while a release would be nice, I think the timestamp thing is a
significant enough change that it'd be good to have it in an RC release
before final.
Doug Cutting wrote:
> Should I go ahead and make this release, or should we wait for a fix to
> the timestamp problem? I'm leaving town Thursday, and can either make
> this release tomorrow morning, or not until November. My hunch is to go
> ahead and make an RC release tomorrow, then, in November, when the
> timestamp problem is resolved, make a 1.3 final release. Does that
> sound like a good plan?
>
> Doug
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by petite_abeille <pe...@mac.com>.
On Tuesday, Oct 21, 2003, at 20:52 Europe/Amsterdam, Doug Cutting wrote:
> Should I go ahead and make this release, or should we wait for a fix
> to the timestamp problem? I'm leaving town Thursday, and can either
> make this release tomorrow morning, or not until November. My hunch
> is to go ahead and make an RC release tomorrow, then, in November,
> when the timestamp problem is resolved, make a 1.3 final release.
> Does that sound like a good plan?
+++++1 :)
Cheers,
PA.
--
http://zoe.nu/
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Otis Gospodnetic <ot...@yahoo.com>.
Definitely +1 for the hunch.
Otis
--- Doug Cutting <cu...@lucene.com> wrote:
> Should I go ahead and make this release, or should we wait for a fix
> to
> the timestamp problem? I'm leaving town Thursday, and can either
> make
> this release tomorrow morning, or not until November. My hunch is to
> go
> ahead and make an RC release tomorrow, then, in November, when the
> timestamp problem is resolved, make a 1.3 final release. Does that
> sound like a good plan?
>
> Doug
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
Re: 1.3 RC2
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
+1
On Tuesday, October 21, 2003, at 02:52 PM, Doug Cutting wrote:
> Should I go ahead and make this release, or should we wait for a fix
> to the timestamp problem? I'm leaving town Thursday, and can either
> make this release tomorrow morning, or not until November. My hunch
> is to go ahead and make an RC release tomorrow, then, in November,
> when the timestamp problem is resolved, make a 1.3 final release.
> Does that sound like a good plan?
>
> Doug
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org