: Subject: RE: jira tracking of issues fixed in 4.0-ALPHA FYI: I finally got a cahnce to deal with this today, and (of course) realized it wa more complicated then Uwe and i had originally thought -- for people interested in the specifics, the details of exactly what were done are listed at the bottom (i worked it out with Uwe on IRC).
In short: it was a huge pain in the ass.
The lesson to learn here is that if/when we release a 4.0-BETA we should
*IMMEDIATELY* ...
1) rename "4.0" to "4.0-BETA" in jira and mark it released
2) add a new "4.0"
...if we had done that for 4.0-ALPHA it would have prevented lots of
headaches and saved ~2 hours of time
---- How Hoss Spent His Day -----
In Jira project admin for both SOLR and LUCENE...
1) merge version "4.0-ALPHA" -> "4.0"
- do this instead of delete to preserve "affects=4.0-ALPHA"
2) rename version "4.0" to "4.0-ALPHA"
- keeps the versionId for (old) 4.0 and gives it to 4.0-ALPHA
3) add a new version "4.0"
4) bulk update "resolution=unresolved && fixVersion=4.0-ALPHA" -> set
fixVersion=4.0
- do this before marking 4.0-ALPHA as "released"
- if jira does it automaticly there is no way to stop emails
- use "hoss20120711-bulk-40-change" in comment
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LUCENE+AND+resolution+%3D+Unresolved+and+fixVersion%3D%224.0-ALPHA%22
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SOLR+AND+resolution+%3D+Unresolved+and+fixVersion%3D%224.0-ALPHA%22
5) mark "4.0-ALPHA" as "released"
6) manually update any issues listed in CHANGES after Alpha to set
fixVersion=4.0
- use "hoss20120711-manual-post-40alpha-change" in comment
Issues manually edited...
https://issues.apache.org/jira/browse/SOLR-1856
https://issues.apache.org/jira/browse/SOLR-3559
https://issues.apache.org/jira/browse/SOLR-1929
https://issues.apache.org/jira/browse/SOLR-3562
https://issues.apache.org/jira/browse/SOLR-2616
https://issues.apache.org/jira/browse/SOLR-3582
https://issues.apache.org/jira/browse/SOLR-3467
https://issues.apache.org/jira/browse/SOLR-3587
https://issues.apache.org/jira/browse/SOLR-3610
https://issues.apache.org/jira/browse/SOLR-1770
https://issues.apache.org/jira/browse/SOLR-3355
https://issues.apache.org/jira/browse/SOLR-3575
https://issues.apache.org/jira/browse/SOLR-3563
https://issues.apache.org/jira/browse/SOLR-3599
--
https://issues.apache.org/jira/browse/LUCENE-4201
https://issues.apache.org/jira/browse/LUCENE-4185
https://issues.apache.org/jira/browse/LUCENE-3832
https://issues.apache.org/jira/browse/LUCENE-4138
https://issues.apache.org/jira/browse/LUCENE-4178
https://issues.apache.org/jira/browse/LUCENE-4171
https://issues.apache.org/jira/browse/LUCENE-4184
https://issues.apache.org/jira/browse/LUCENE-4176
https://issues.apache.org/jira/browse/LUCENE-4094
https://issues.apache.org/jira/browse/LUCENE-4189
https://issues.apache.org/jira/browse/LUCENE-4110
https://issues.apache.org/jira/browse/LUCENE-4160
https://issues.apache.org/jira/browse/LUCENE-4115
https://issues.apache.org/jira/browse/LUCENE-4199
https://issues.apache.org/jira/browse/LUCENE-4202
https://issues.apache.org/jira/browse/LUCENE-4206
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
