###############################################################################
#
# Mantevo Suite Framework-level Release Process Checklist
#
# Version 12/2012
#
###############################################################################

Plan:

1.1 Announce target release date via the Mantevo-Developers mail list.
    Target Release Date:

1.2 Send developers the proxyapp release checklist for first-time release
    proxyapps.

1.3 Verify that licensing of new proxyapps is LGPL, BSD, or MIT.  If not,
    consult legal for a determination on compatibility with the Mantevo Suite.

1.4 Finalize the list of proxyapps to be included in the release with the
    development team and project leader.

1.5 Send developers a reminder concerning release announcement contributions
    and proxyapp-specific release notes.

Do:

2.1 Collect 2 tarballs for the release from each participating proxyapp:
    1) Reference version 2) Version that includes all variants to be released
    Add the tarballs to the Mantevo Suite tarball repository.

2.2 Perform testing as appropriate or request by developers.  Developers are
    primarily responsible for testing, but may request assistance.  Listing of 
    completed testing:

2.3 Collect all release announcement contributions and proxyapp-specific release
    notes.

2.4  Approve the release (Project Leader, or Release Coordinator).

2.5 Add any new proxy apps to the Packages and possibly Applications pages.

2.6 List first time release proxyapps under the appropriate license on
    the License page.

2.7 Add the release announcement and release notes to the Release Notes page.

2.8 Add links to all release tarballs on the downloads page.  Add some form
    of download tracking if possible.

2.9 Add the release to the News page and homepage.

Check:

3.1 Test all pages updated as part of the "Do" section.  Commit the pages to
    the repository if not already done.

3.2 Send a note to the development team informing them that they can take a
    look at the site and verify everything is there that they wanted.

Act:

4.1 Tag the current version of the Mantevo SVN repository.  This tag may not
    reflect the exact version of some proxyapps, in fact some are not stored
    in this repository at all, but the tag may still be useful in the future.
    The tag should be similar to mantevo-release-1-0.  Tag: 

4.2 Announce the release (user/announce lists, NA Digest, other?). Date:

General Instructions:
This checklist describes Mantevo-level activities that are associated with the
Mantevo release process.  The steps may be completed by any team member unless
otherwise noted.  Steps do not need to be completed in the exact order listed
and can be combined when appropriate.  If a step or a portion of a step is not
applicable to a particular release, that should be noted.

The process initiation date will be considered the date on which the Process
Checklist is first entered into an issue tracking tool.  The process shall be
considered complete when the associated issue is closed.

Process Ownership:
This document and associated procedure are owned by the Mantevo Project Leader
who must approve any changes.  This document is under version control.  This
document version supersedes all previous versions.

Authority to perform process:
Any team member may initiate this procedure. 

If this process or associated document is superseded after an activity has been
initiated, the process shall be completed under this version unless
specifically notified by the Mantevo Project Leader.

Stage Entrance and Stage Exit:
The stage entrance is the process initiation by any authorized person. All
necessary process inputs are built into the checklist.  The stage exit is the
completion of this form (all steps completed and required metrics entered)
and the closure of the associated issue.