lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "ReleaseTodo" by MikeMcCandless
Date Fri, 26 Aug 2016 14:07:01 GMT
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 MikeMcCandless:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=241&rev2=242

  == 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). 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.  This URL may work (but edit the fixVersion
part): (https://issues.apache.org/jira/issues/?jql=project+in+(LUCENE,SOLR)+AND+status=Resolved+AND+fixVersion=6.0.1).
 Do a bulk change (Under Tools... menu) 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 (this URL may work - but edit the fixVersion part
- https://issues.apache.org/jira/issues/?jql=project+in+(LUCENE,SOLR)+AND+resolution=Unresolved+AND+fixVersion=6.0.1),
and do a bulk change to the fixVersion to be both the master version and the next version
on the branch you just released from.  Uncheck the box that says "send an email for these
changes".
+  1. Do another JIRA search to find all issues with Unresolved Resolution and fixVersion
of the release you just made.  Note that Jira can only bulk-change fixVersion if you search
only one project at a time.  This URL may work - but edit the fixVersion part, and change
LUCENE to SOLR to get to Solr's issues separately - https://issues.apache.org/jira/issues/?jql=project+=+LUCENE+AND+resolution=Unresolved+AND+fixVersion=6.0.1,
and do a bulk change to the fixVersion to be both the master version and the next version
on the branch you just released from.  Uncheck the box that says "send an email for these
changes".
   1. Add a new Version for the next possible release version on the "Manage Versions" Administration
page (https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions). e.g.
If the current release is 5.2.1, add 5.2.2 with a description so that contributors can commit
to the release branch with the next release version. In case of a minor release e.g. 5.2,
this step needs to be done when the new release branch is cut.
  
  == Stop mirroring old releases ==

Mime
View raw message