Use of fix version

[Jack Krupansky <ja...@basetechnology.com>]

"all issues with Unresolved Resolution and fixVersion of the release you 
just made, and do a bulk change to the fixVersion to be both the trunk 
version and the next version on the branch you just released from.  Uncheck 
the box that says "send an email for these changes"."

It seems to me that a lot of issues are indicated to be fixed in the next 
dot release when they are in fact very unlikely to be fixed in the next dot 
release - or necessarily in trunk for that matter. Could someone explain the 
rationale? I mean, shouldn't "Fix Version: 4.8" mean that there is a very 
high likelihood of resolution in 4.8, rather than mere wishful thinking or 
bulk bureaucratic assignment? I mean, wouldn't it make more sense to use a 
more "agile" methodology, with most issues being in an unassigned "backlog", 
and being very selective what is targeted for the current "sprint"/next dot 
release? Ditto for trunk - shouldn't it be more selective so that we can see 
how close we are to finishing the high priority issues needed for a trunk 
release?

I mean, how useful is fix version in its current form?

And maybe there needs to be special formatting to highlight the importance 
of "Uncheck the box that says "send an email for these changes"."", although 
the omission of that step did highlight the main issue I mentioned.

-- Jack Krupansky

-----Original Message----- 
From: Apache Wiki
Sent: Sunday, March 16, 2014 9:06 AM
To: Apache Wiki
Subject: [Lucene-java Wiki] Update of "ReleaseTodo" by DavidSmiley

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" 
for change notification.

The "ReleaseTodo" page has been changed by DavidSmiley:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=165&rev2=166

Comment:
Releasing in JIRA requires more choosing the "Release" option. And clarify 
to not transition issues then.

  = Post-release =

  == Update JIRA ==
-  1. Go to the JIRA "Manage Versions" Administration pages 
(https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions 
and 
https://issues.apache.org/jira/plugins/servlet/project-config/SOLR/versions), 
click on the release date field for the version you just released, put in 
the release date, and then click the "Update" button.
+  1. Go to the JIRA "Manage Versions" Administration pages 
(https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions 
and 
https://issues.apache.org/jira/plugins/servlet/project-config/SOLR/versions). 
Next to the version you'll release, click the gear pop-up menu icon and 
choose "Release".  It will ask you for the release date -- enter it.  It 
will give the option of transitioning issues marked fix-for the released 
version to the next version, but do '''not''' do this as it will send an 
email for each issue -- we'll address that separately.
-  1. Go to JIRA search in both Solr and Lucene and find all issues that 
were fixed in the release you just made, whose Status is Resolved, and do a 
bulk change to close all of these issues. Uncheck the box that says "send an 
email for these changes".
+  1. Go to JIRA search in both Solr and Lucene and find all issues that 
were fixed in the release you just made, whose Status is Resolved, and do a 
bulk change to close all of these issues (this is a workflow transition 
task). Uncheck the box that says "send an email for these changes".
   1. Do another JIRA search in both Solr and Lucene to find all issues with 
Unresolved Resolution and fixVersion of the release you just made, and do a 
bulk change to the fixVersion to be both the trunk version and the next 
version on the branch you just released from.  Uncheck the box that says 
"send an email for these changes".

  == Don't mirror old releases == 


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

Re: Use of fix version

["David Smiley (@MITRE.org)" <DS...@mitre.org>]

Jack Krupansky-2 wrote
> And maybe there needs to be special formatting to highlight the importance 
> of "Uncheck the box that says "send an email for these changes"."",
> although 
> the omission of that step did highlight the main issue I mentioned.

My error was not neglecting to see that, it was letting JIRA bump the
fix-for versions as part of choosing "Release" menu next to the version in
the version screen.  So I added explicit instructions on the choice on the
wiki.

Sorry again.

To your larger point of fix-for versions... we can't stop users using them
how we might want them to be used, so there's little benefit in trying to
have it reflect some particular meaning (i.e. it really really will be
likely to be done by fix-for version).

~ David




-----
 Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in context: http://lucene.472066.n3.nabble.com/Use-of-fix-version-tp4124560p4124561.html
Sent from the Lucene - Java Developer mailing list archive at Nabble.com.

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