This makes it relatively safe for people to grab a snapshot of the trunk
with less >concern about latent bugs.
I think the concern is that if we start doing this stuff on trunk now,
people that are >accustomed to snapping from the trunk might be surprised, and not in a good way. +1 on this. There are some great performance improvements in 2.0.1 Peter On 10/17/06, Steven Parkes <[EMAIL PROTECTED]> wrote:
I think the idea is that 2.0.1 would be a patch-fix release from the branch created at 2.0 release. This release would incorporate only back-ported high-impact patches, where "high-impact" is defined by the community. Certainly security vulnerabilities would be included. As Otis said, to date, nobody seems to have raised any issues to that level. 2.1 will include all the patches and new features that have been committed since 2.0; there've been a number of these. But releases are done pretty ad hoc at this point and there hasn't been anyone that has expressed strong interest in (i.e., lobbied for) a release. There was a little discussion on this topic at the ApacheCon BOF. For a number of reasons, the Lucene Java trunk has been kept "pretty stable", with a relatively few number of large changes. This makes it relatively safe for people to grab a snapshot of the trunk with less concern about latent bugs. I don't know how many people/projects are doing this rather than sticking with 2.0. Keeping the trunk stable doesn't provide an obvious place to start working on things that people may want to work on and share but at the same time want to allow to percolate for a while. I think the concern is that if we start doing this stuff on trunk now, people that are accustomed to snapping from the trunk might be surprised, and not in a good way. Nobody wants that. So releases can be about both what people want (getting features out) and allowing a bit more instability in trunk. That is, if the community wants that. Food for thought and/or discussion? -----Original Message----- From: George Aroush [mailto:[EMAIL PROTECTED] Sent: Sunday, October 15, 2006 5:15 PM To: java-user@lucene.apache.org Subject: RE: Lucene 2.0.1 release date Thanks for the reply Otis. I looked at the CHANGES.txt file and saw quit a bit of changes. For my port from Java to C#, I can't rely on the trunk code as it is (to my knowledge) changes on a monthly basic if not weekly. What I need is an official release so that I can use it as the port point. Regards, -- George Aroush -----Original Message----- From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: Sunday, October 15, 2006 12:41 AM To: java-user@lucene.apache.org Subject: Re: Lucene 2.0.1 release date I'd have to check CHANGES.txt, but I don't think that many bugs have been fixed and not that many new features added that anyone is itching for a new release. Otis ----- Original Message ---- From: George Aroush <[EMAIL PROTECTED]> To: java-dev@lucene.apache.org; java-user@lucene.apache.org Sent: Saturday, October 14, 2006 10:32:47 AM Subject: RE: Lucene 2.0.1 release date Hi folks, Sorry for reposting this question (see original email below) and this time to both mailing list. If anyone can tell me what is the plan for Lucene 2.0.1 release, I would appreciate it very much. As some of you may know, I am the porter of Lucene to Lucene.Net knowing when 2.0.1 will be released will help me plan things out. Regards, -- George Aroush -----Original Message----- From: George Aroush [mailto:[EMAIL PROTECTED] Sent: Thursday, October 12, 2006 12:07 AM To: java-dev@lucene.apache.org Subject: Lucene 2.0.1 release date Hi folks, What's the plan for Lucene 2.0.1 release date? Thanks! -- George Aroush --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
