Releasing Emma's maven plugin.
---------------------------------

Steps to make a new release:

- Ensure unit tests pass, using procedures in BUILD.txt

- Ensure all dependencies (version of emma and emma-ant that are used)
  are uploaded to ibiblio and emma.sf.net/maven/emma/jars
  See http://maven.apache.org/reference/repository-upload.html
  for instructions.
  - There are projects to create EMMA bundles, in CVS at
    /plugins/maven/upload/
  - You need to update these projects with the versions for the bundles to
    be created
  - Bundles can be made available at emma.sf.net/maven/emma/bundles
  - IMPORTANT NOTE: currently there seems to be a bug in the bundle creation
    plugin that creates empty jars in the bundle.  You need to manually replace with 
    the correct jar before uploading.

- Update project.xml to remove -SNAPSHOT from version to be released
  
- Get a report of all bugs/enhancements in the release:
  - In SourceForge bug and RFE trackers, search by
    group = implemented/checked in
  - make a note of the issue numbers/descriptions
    (to be used later in the release notes)
  - append to this list bugfixes/enhancements made
    in the previous releases (get them from the release notes)

- Build the plugin, following procedures in BUILD.txt

- Upload the plugin to ibiblio and emma.sf.net/maven/emma/plugins.
  See steps above for ibiblio upload procedure, and use the maven-emma-plugin-ibiblio-upload project.
  Make sure you update the dependency versions for EMMA in project.xml

- upload ...\target\maven-emma-plugin-x.y.jar to upload.sourceforge.net/incoming
  (Note: do not forget to use ftp binary mode)

- publish new files on sourceforge
    - Admin - File Releases - Login - Add Release
    - Enter new release name: maven-1.0-plugin-x.y
    - Edit new Release
        - Step 1: Enter Release Notes - submit refresh (it usually helps to check "Preserve my pre-formatted text")
          (Note: you may wish to save the release notes text in a file,
          to be reused later for a new project news item and EMMA-announce email)
        - Step 2: Add jar that you just uploaded (jar)
        - Step 3: Edit files - platform independent, jar
        - Step 4: check "I'm sure" and press "Send Notice" to send a notice
          of this new release to all users monitoring EMMA file releases

- do a sniff test of the new file release by going to the "Files" tab in EMMA SourceForge
  project page:
    - verify that the release notes text is correct
    - do a test download and verify that the contents match your expectations
    
- WAIT for uploads to appear on ibiblio (may take a day or so)

- create news item on sourceforge summary page with release notes (used the text
  file created above)
  
- send a message to EMMA-announce list (message contents are identical to
  the above news items)

- tag the plugins/maven and plugins/maventesting trees in CVS
  as MAVEN_1_0_STABLE_x_y
	
- Edit project.xml to show next upcoming version (with -SNAPSHOT appended):
    - project - currentVersion
    - project - versions
    
- commit project.xml

- Close all bugs/enhancements in the release:
  - In SourceForge bug tracker, enter a new group
    (admin link) named "release fixed: plugin x.y
  - In SourceForge bug tracker, search by
    group = implemented/checked in
  - Change "Resolution" to fixed, "Status" to closed, and "Group" 
    to the "release fixed..." value you just created
    
