In general wearing the RM hat has been painless, thanks to the release_commands.pl tool. Thanks for that, Marvin.
Some things I had to hunt around for during the actual release process follow. * this step from the release_commands.pl output is wrong: # Update the issue tracker. # While logged into JIRA, visit the following web page. (Note: this # permalink may or may not work. Please let the dev list know one # way or the other.) Click the "release" link for 0.2.2 and # input the date from the CHANGES file. https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310501 I am "letting the dev list know" in this email. I ended up finding the right place to update the release version by going to: https://issues.apache.org/jira/secure/project and clicking around. * updating the i.a.o/lucy/download.html page took some hunting. I never found a clear one-page summary of how to do it. What I did was: * svn co https://svn.apache.org/repos/asf/incubator/lucy/site * edit site/trunk/content/lucy/download.mdtext * svn commit download.mdtext * wait for buildbot email to indicate staging was updated * svn co https://svn.apache.org/repos/infra/websites/production/lucy prod-site * svn co https://svn.apache.org/repos/infra/websites/staging/lucy stage-site * cp stage-site/trunk/content/lucy/download.html prod-site/content/lucy * svn commit prod-site/content/lucy/download.html Hope that helps the next person. -- Peter Karman . http://peknet.com/ . [email protected]
