| 1 | =================================================== |
|---|
| 2 | Release procedure for the MEV Launcher package |
|---|
| 3 | =================================================== |
|---|
| 4 | |
|---|
| 5 | Follow these instructions to release version A.B of |
|---|
| 6 | this package. Please update the instructions if you |
|---|
| 7 | find anything that is not correct or missing. |
|---|
| 8 | |
|---|
| 9 | 1. Make sure that all changes have been committed to |
|---|
| 10 | the trunk. Check with other developers if not |
|---|
| 11 | sure. |
|---|
| 12 | |
|---|
| 13 | 2. Update the version number. |
|---|
| 14 | |
|---|
| 15 | In build.xml: |
|---|
| 16 | <property name="version" value="A.B" /> |
|---|
| 17 | <property name="depend.base-version" value="X.Y.Z" /> |
|---|
| 18 | |
|---|
| 19 | Run `ant update-version`. This should put the version |
|---|
| 20 | numbers in a lot of files, including, Mev.java and |
|---|
| 21 | META-INF/extensions.xml. |
|---|
| 22 | |
|---|
| 23 | Check (and update if needed) the README file and |
|---|
| 24 | and the wiki pages (see also step 8 and 9 below): |
|---|
| 25 | |
|---|
| 26 | http://baseplugins.thep.lu.se/wiki/net.sf.basedb.mev |
|---|
| 27 | http://baseplugins.thep.lu.se/wiki/PluginDownload |
|---|
| 28 | |
|---|
| 29 | 3. Make sure that the code compiles and can be packaged. |
|---|
| 30 | |
|---|
| 31 | ant package |
|---|
| 32 | |
|---|
| 33 | will create the file 'mev-launcher-A.B.tar.gz' in |
|---|
| 34 | the project directory. |
|---|
| 35 | |
|---|
| 36 | 4. Make sure that the installation of the MEV Launcher works |
|---|
| 37 | and that the installation instructions are up to date. |
|---|
| 38 | |
|---|
| 39 | 5. When everything is OK, commit any changes to subversion. |
|---|
| 40 | |
|---|
| 41 | 6. Create a tag in subversion: |
|---|
| 42 | |
|---|
| 43 | svn copy http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.mev/trunk \ |
|---|
| 44 | http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.mev/tags/A.B \ |
|---|
| 45 | -m "Tagging release A.B" |
|---|
| 46 | |
|---|
| 47 | 7. Upload the packaged release as an attachment to: |
|---|
| 48 | http://baseplugins.thep.lu.se/wiki/net.sf.basedb.mev |
|---|
| 49 | |
|---|
| 50 | 8. Edit the http://baseplugins.thep.lu.se/wiki/net.sf.basedb.examples.mev |
|---|
| 51 | page: |
|---|
| 52 | |
|---|
| 53 | * Add a new entry to the Download table |
|---|
| 54 | * Change the README link to point to the tagged release. Use |
|---|
| 55 | the following wiki code: |
|---|
| 56 | [source:/extensions/net.sf.basedb.mev/tags/A.B/README README] |
|---|
| 57 | * Check the information on the download page |
|---|
| 58 | http://baseplugins.thep.lu.se/wiki/PluginDownload |
|---|
| 59 | and make sure it is correct |
|---|
| 60 | |
|---|
| 61 | 9. Create a new milestone: 'MEV Launcher vA.B+1' |
|---|
| 62 | |
|---|
| 63 | 10. Close the 'MEV Launcher A.B' milestone. Move |
|---|
| 64 | any remaining tickets to the newly create milestone. |
|---|
| 65 | |
|---|
| 66 | 11. Update the version numbers. |
|---|
| 67 | |
|---|
| 68 | In build.xml: <property name="version" value="A.(B+1)-dev" /> |
|---|
| 69 | Run `ant update-version` and commit the changes to |
|---|
| 70 | subversion: |
|---|
| 71 | |
|---|
| 72 | svn commit -m "Preparing for future release A.B+1" |
|---|
| 73 | |
|---|
