Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of markrmiller@gmail.com
 designates 209.85.216.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=COQUdbj+Tq7ODRogrBofXyjDlfWBcegy1JwQBa6p1bOVVn3MwKSMspcWk0sJ8DlBKK
         W5rijA76FNz0geOvAImx+XmfnN/xJHd5fszj+0xINGHmQ1tcuuAVd9aYvPWtaszvSkbK
         VFV3Ncl4dR/B8vJbP9aNjRXsQq73SSkSPEeyQ=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: jira issues falling off the radar -- "Next" JIRA version
From: Mark Miller <markrmiller@gmail.com>
In-Reply-To: <alpine.DEB.2.00.1105051219330.27121@bester>
Date: Thu, 5 May 2011 15:45:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D35BA1DC-7BFE-44D7-B1CD-7F1CA6D8AADF@gmail.com>
References: <33278567.49101287938900125.JavaMail.jira@thor>
 <199660262.10603.1304037963299.JavaMail.tomcat@hel.zones.apache.org>
 <1304050373532-2878021.post@n3.nabble.com>
 <BANLkTimjo_VCQr62qdiwmQ64U+BsE5s7MQ@mail.gmail.com>
 <alpine.DEB.2.00.1105021623460.28424@bester>
 <A2D3A77E-4C3A-4FD7-A6E5-37AC22DCD225@mitre.org>
 <alpine.DEB.2.00.1105051219330.27121@bester>
To: dev@lucene.apache.org

+1 - next should be nuked, the issues should simply be plopped into the =
next likely release and dealt with (done, moved, pushed) before release.


On May 5, 2011, at 3:24 PM, Chris Hostetter wrote:

>=20
> : > We should definitely kill of "Next" ... i would suggest just =
removing it,=20
> : > and not bulk applying a new version (there is no requirement that =
issues=20
> : > have a version)
> 	...=20
> : Based on that, I think it would be irresponsible to just delete =
"Next"=20
> : because any issues assigned to this version on the basis of that=20
> : description (like SOLR-2191) is going to be dropped on the floor.
>=20
> Of course you're right ... i was thinking about it from a "what's the=20=

> minimum that must be done in order to eliminate a version, but that=20
> doesn't mean it would leave those issues in a good state.
>=20
> Doing a little more reading about Jira version management, I realized =
that=20
> Jira allows Versions to be "merged"
>=20
> I suggest we marge "Next" into "3.2" ...
>=20
> =
http://confluence.atlassian.com/display/JIRA/Managing+Versions#ManagingVer=
sions-Mergingmultipleversions
>=20
>=20
> 	...objections?
>=20
>=20
>=20
> -Hoss
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>=20

- Mark Miller
lucidimagination.com

Lucene/Solr User Conference
May 25-26, San Francisco
www.lucenerevolution.org


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