======================================================== Release procedure for the External files support package ======================================================== Follow these instructions to release version A.B of this package. Please update the instructions if you find anything that is not correct or missing. 1. Make sure that all changes have been committed to the trunk. Check with other developers if not sure. 2. Update the version number. In build.xml: Run `ant update-version`. This should put the version numbers in a lot of files, including, META-INF/extensions.xml. Check (and update if needed) the README file and and the wiki pages (see also step 8 and 9 below): http://baseplugins.thep.lu.se/wiki/net.sf.basedb.xfiles http://baseplugins.thep.lu.se/wiki/PluginDownload 3. Make sure that the code compiles and can be packaged. ant package will create the file 'xfiles-A.B.tar.gz' in the project directory. 4. Make sure that the installation of this extension works and that the installation instructions are up to date. 5. When everything is OK, commit any changes to subversion. 6. Create a tag in subversion: svn copy http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.xfiles/trunk \ http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.xfiles/tags/A.B \ -m "Tagging release A.B" 7. Upload the packaged release as an attachment to: http://baseplugins.thep.lu.se/wiki/net.sf.basedb.xfiles 8. Edit the http://baseplugins.thep.lu.se/wiki/net.sf.basedb.xfiles page: * Add a new entry to the Download table * Change the README link to point to the tagged release. Use the following wiki code: [source:/extensions/net.sf.basedb.xfiles/tags/A.B/README README] * Check the information on the download page http://baseplugins.thep.lu.se/wiki/PluginDownload and make sure it is correct 9. Create a new milestone: 'External files support A.B+1' 10. Close the 'External files support A.B' milestone. Move any remaining tickets to the newly create milestone. 11. Update the version numbers. In build.xml: Run `ant update-version` and commit the changes to subversion: svn commit -m "Preparing for future release A.B+1"