[Lucene-java Wiki] Update of "ReleaseTodo" by SteveRowe

[Apache Wiki <wi...@apache.org>]

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 SteveRowe:
https://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=243&rev2=244

Comment:
Move DOAP update section to its own top-level item, and update the location of the files to be edited

    * The safest way is to svn checkout https://svn.apache.org/repos/asf/lucene/cms/trunk/ and use find/grep for the previous release, add entries, and then svn commit
     . and look at the staging website (http://lucene.staging.apache.org). Javadocs wont work because they go directly to production (see above) but you can check everything else this way.
    * Be sure to update the version in {{{content/latestversion.mdtext}}}
-  1. Update the core & solr doap.rdf files to reflect the new versions using the Apache CMS
-   * https://cms.apache.org/redirect?uri=http://lucene.apache.org/core/doap.rdf
-   * https://cms.apache.org/redirect?uri=http://lucene.apache.org/solr/doap.rdf
   1. Immediately after committing your changes, you should see the CMS buildbot kick off a new build here at https://ci.apache.org/builders/lucene-site-staging After that finishes, you should load http://lucene.staging.apache.org and verify your changes look OK, and iterate if not.  Be sure your browser is not caching an old copy!
   1. If for some reason your changes fail to show up at http://lucene.staging.apache.org, try editing a template file, e.g. add harmless whitespace to http://svn.apache.org/repos/asf/lucene/cms/trunk/templates/core-sidebar.html because this could provoke the buildbot into trying harder (do a "clean" build)
   1. Once all is good on staging, publish the site, e.g. by visiting http://lucene.staging.apache.org, invoking the [[https://cms.apache.org/#bookmark|CMS bookmarklet]], then clicking the publish link.  Or just go straight here: https://cms.apache.org/lucene/publish
@@ -285, +282 @@

  templates/sidenav.mdtext
  templates/solr-index.html
  }}}
+ 
+ = Update the project DOAP files =
+ 
+ Update the Core & Solr DOAP RDF files on the unstable and stable branches to reflect the new versions (note that the website {{{.htaccess}}} file redirects from their canonical URLs to their locations in the Lucene/Solr Git source repository - see {{{dev-tools/doap/README.txt}}} for more info):
+  * {{{dev-tools/doap/lucene.rdf}}}
+  * {{{dev-tools/doap/solr/doap.rdf}}}
  
  = Announce the Release =
  Release announcements can be shared/edited on the wiki at http://wiki.apache.org/lucene-java/ReleaseNoteXY(Z) and http://wiki.apache.org/solr/ReleaseNoteXY(Z)
@@ -373, +376 @@

   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 ==
  Shortly after new releases are first mirrored, they are automatically copied to the archives.  Only the latest point release from each active branch should be kept under the Lucene PMC svnpubsub area {{{dist/releases/lucene/}}} and {{{dist/releases/solr/}}}.  Older releases can be safely deleted, since they are already backed up in the archives.