===================================================
Release procedure for the MEV Launcher 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: <property name="version" value="A.B" />
    * In META-INF/extensions.xml: <version>A.B</version>

 3. Make sure that the code compiles and can be packaged.
 
    ant package
    
    will create the file 'mev-launcher-A.B.tar.gz' in
    the project directory.
 
 4. Make sure that the installation of the MEV Launcher 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.mev/trunk \
        http://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.mev/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.mev

 8. Edit the http://baseplugins.thep.lu.se/wiki/net.sf.basedb.examples.mev 
    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.mev/tags/A.B/README README]

 9. Create a new milestone: 'MEV Launcher vA.B+1'

10. Close the 'MEV Launcher A.B' milestone. Move
    any remaining tickets to the newly create milestone.

11. Update the version number in build.xml.

    <property name="version" value="A.B+1" />
    
    Commit the change to subversion: 
    
    svn commit -m "Preparing for future release A.B+1"