lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: releases
Date Thu, 26 Oct 2006 03:03:42 GMT
Steven,

I don't recall any commits in the lucene_2_0 branch, I think everything since 2.0 has been
getting committed in the trunk, and my guess is those are just human errors in JIRA.  But
I think your interpretation of how Fix Versions should be read is correct.

Otis

----- Original Message ----
From: Steven Parkes <steven_parkes@esseff.org>
To: java-dev@lucene.apache.org
Sent: Wednesday, October 25, 2006 1:41:05 PM
Subject: releases

A question about releases, mostly with respect to Jira, I guess.

There a number of resolved Jira issues that spec the Fix Version/s as
2.0.1. I'm wondering if I'm interpreting this correctly: to me, this
would mean that the changes have been checked into branches/lucene_2_0,
not trunk. But these were actually checked into trunk. As far as the
changes go, that's what I expect. Unless there's a great demand for it
(like some horrendous security bug), I don't expect there ever will be a
2.0.1. But as far as Jira resolved issues goes, Fix Version/s 2.0.1
should mean checked into branches/lucene_2_0 and Fix Version/s 2.1
should mean checked into trunk (until there is a 2.1 release)?




---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-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


Mime
View raw message