Re: Lucene 1.9 release date?

[Ray Tsang <sa...@gmail.com>]

Hi All,

I think this release issue died out again.  I noticed an increase in
commit activities recently!  I've also noticed the release plan for
2.0 on the wiki.  Does current 1.9 already meet the criterias for 2.0?
At least API-wise?  If so, is it possible to make ways for a release?
at least marking the API stable, setting a feature freeze, and make
release candidates?

Also, I mentioned before about a Tracker bug regarding the 1.9
release.  In JIRA, we should mark all other versions as 'released',
and move 1.9 up to the front of version list.  This way, JIRA will
collapse all the other versions and only show open issues related to
1.9 release.

Ray,


On 10/16/05, Ray Tsang <sa...@gmail.com> wrote:
> How about setting some preliminary due dates, so that things don't
> just hang there.
>
> ray,
>
> On 10/15/05, Otis Gospodnetic <ot...@yahoo.com> wrote:
> > Re Votes - yes, please use that feature to help prioritize.
> >
> > Otis
> >
> > --- Ray Tsang <sa...@gmail.com> wrote:
> >
> > > Ah I see it.  Should we start assigning and voting for issues that
> > > should make it into the 1.9 release?  Maybe set a due date for
> > > submitting these 1.9-bound issues, a week for voting and review, and
> > > then allocate time for applying the patches.  I can't wait to see an
> > > officially released 1.9!
> > >
> > > Also, I think Jira can make a distinction between released and
> > > unreleased versions?
> > >
> > > ray,
> > >
> > > On 10/15/05, Erik Hatcher <er...@ehatchersolutions.com> wrote:
> > > > On Oct 14, 2005, at 11:06 PM, Ray Tsang wrote:
> > > > > Can we add a 1.9 release to the roadmap? or start a 1.9 release
> > > > > tracker issue?
> > > >
> > > > If you mean the ability to log issues on JIRA for 1.9, I created
> > > that
> > > > several weeks ago.  Let me know if something still isn't right.
> > > >
> > > >      Erik
> > > >
> > > >
> > > >
> > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> > > > For additional commands, e-mail: java-user-help@lucene.apache.org
> > > >
> > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-dev-help@lucene.apache.org
> >
> >
> >
>

Re: Lucene 1.9 release date?

[Erik Hatcher <er...@ehatchersolutions.com>]

On Dec 5, 2005, at 2:03 AM, Ray Tsang wrote:
> I think this release issue died out again.  I noticed an increase in
> commit activities recently!  I've also noticed the release plan for
> 2.0 on the wiki.  Does current 1.9 already meet the criterias for 2.0?
> At least API-wise?  If so, is it possible to make ways for a release?
> at least marking the API stable, setting a feature freeze, and make
> release candidates?

As far as I know, the current trunk is ready for release, waiting for  
a release manager volunteer.  I'm all for a release.

The only thing I have on my plate is to move the (Span)RegexQuery to  
contrib/regex, which I'll be doing this week.

> Also, I mentioned before about a Tracker bug regarding the 1.9
> release.  In JIRA, we should mark all other versions as 'released',
> and move 1.9 up to the front of version list.  This way, JIRA will
> collapse all the other versions and only show open issues related to
> 1.9 release.

I have just marked all the other versions as released in JIRA.  It  
still shows 1.9 under the "unreleased" area at the bottom of the  
list, though.  I'm not sure how to change that.  Once 1.9 is marked  
as released it will appear at the top as it is listed as the latest,  
but it groups into released and unreleased with no option (that I can  
see) to order those.

	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org