-- Feature freeze from Wednesday (06/06)
All features must be checked in by end of Tuesday. On Wednesday I will
Michael, is there a need to hold commits to trunk while
the new branch is created?
(This is with LUCENE-912 and LUCENE-913 in mind - I think
they can wait for 2.3, there would
Doron Cohen wrote:
Michael, is there a need to hold commits to trunk while
the new branch is created?
No, normal trunk development may continue as usual.
(This is with LUCENE-912 and LUCENE-913 in mind - I think
they can wait for 2.3, there would always be new issues.)
I haven't
On 6/6/07, Michael Busch [EMAIL PROTECTED] wrote:
I haven't branched the trunk yet (I will send a different mail to this
list afterwards).
Since the patches are in place we might want to commit LUCENE-912 and
LUCENE-913 before?
+1, these are medium-serious bugs with fixes that look unlikely to
Michael Busch wrote:
I haven't branched the trunk yet (I will send a different mail to this
list afterwards).
Since the patches are in place we might want to commit LUCENE-912 and
LUCENE-913 before?
If there are no objections I plan to commit it later today.
Doron Cohen wrote:
If there are no objections I plan to commit it later today.
+1. Thanks for taking care of these, Doron!
I'm working on LUCENE-908 in parallel. After all three are committed
(908, 912, 913)
I will make the branch.
Doron Cohen wrote:
Since the patches are in place we might want to commit LUCENE-912 and
LUCENE-913 before?
If there are no objections I plan to commit it later today.
912 and 913 are committed. Great job, Doron! Thank you!
Alright, everything seems to be in place. Good timing! I
+1
If this new process goes well (which it seems to be), it should be
added to the How To Make a Release
Thanks, Michael, for all your hard work on this.
-Grant
On Jun 4, 2007, at 11:35 PM, Michael Busch wrote:
Hello everyone,
I'd like to suggest a schedule here for the Lucene 2.2
Hello everyone,
I'd like to suggest a schedule here for the Lucene 2.2 release:
-- Feature freeze from Wednesday (06/06)
All features must be checked in by end of Tuesday. On Wednesday I will
branch the trunk and we will have a feature freeze on the branch. Then
only Jira issues with Fix
