source: extensions/net.sf.basedb.mev/trunk/RELEASE @ 1191

Last change on this file since 1191 was 1191, checked in by Nicklas Nordborg, 12 years ago

Preparing release of MeV launcher 1.6

File size: 2.1 KB
Line 
1===================================================
2Release procedure for the MEV Launcher package
3===================================================
4
5Follow these instructions to release version A.B of
6this package. Please update the instructions if you
7find 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: <property name="version" value="A.B" />
16    * In META-INF/extensions.xml: <version>A.B</version>
17    * In src/server/net/sf/basedb/mev/MeV.java: public ... String VERSION = "A.B"
18
19 3. Make sure that the code compiles and can be packaged.
20 
21    ant package
22   
23    will create the file 'mev-launcher-A.B.tar.gz' in
24    the project directory.
25 
26 4. Make sure that the installation of the MEV Launcher works
27    and that the installation instructions are up to date.
28   
29 5. When everything is OK, commit any changes to subversion.
30
31 6. Create a tag in subversion:
32
33    svn copy http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.mev/trunk \
34        http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.mev/tags/A.B \
35        -m "Tagging release A.B"
36
37 7. Upload the packaged release as an attachment to:
38    http://baseplugins.thep.lu.se/wiki/net.sf.basedb.mev
39
40 8. Edit the http://baseplugins.thep.lu.se/wiki/net.sf.basedb.examples.mev
41    page:
42   
43    * Add a new entry to the Download table
44    * Change the README link to point to the tagged release. Use
45      the following wiki code:
46      [source:/extensions/net.sf.basedb.mev/tags/A.B/README README]
47    * Check the information on the download page
48      http://baseplugins.thep.lu.se/wiki/PluginDownload
49      and make sure it is correct
50
51 9. Create a new milestone: 'MEV Launcher vA.B+1'
52
5310. Close the 'MEV Launcher A.B' milestone. Move
54    any remaining tickets to the newly create milestone.
55
5611. Update the version number in build.xml.
57
58    <property name="version" value="A.B+1pre" />
59   
60    Commit the change to subversion:
61   
62    svn commit -m "Preparing for future release A.B+1"
63     
Note: See TracBrowser for help on using the repository browser.