Naming convention

MXP release naming convention is as follows:

mxp-<language>-<protocol_version>-<release_version>-<platform>

Examples of the naming convetion:

1. mxp-java-0.5-0.1-src - for MXP Java implementation supporting MXP protocol 0.5, release version 0.1, source release
2. mxp-cxx-0.5-0.1-linux_x86_64 - for MXP C++ implementation support MXP protocol 0.5, release version 0.1, Linux x86_64

Steps

1. Determine the release version number.
2. Branch the exact release version to SVN.
3. Until no blocker issues, repeat:
   1. Build release candidate.
   2. Package the release candidate.
   3. Publish release candidate.
   4. Test the release candidate.
4. Tag the release in SVN from the branch.
5. Declare the latest release candidate as release.
6. Tag the release to SVN.
7. Rename packages from release candidate to release.
8. Publish packages.
9. Create brief news item to selected feeds about the release.
10. Syndicate news to freshmeat.net - where else?

Publish

1. Publish to: http://code.google.com/p/setp/downloads/list
2. Summary Convention
   1. MXP protocol 0.5 - C# implementation 0.1 - sources - release candidate
   2. MXP protocol 0.5 - C# implementation 0.1 - mono build - release candidate
3. Tags: Type (Source/Library), Language, OpSys, Featured

Packages

1. Separate package for each language and platform combination.
2. Package content:
   1. Readme file
   2. Source release
   3. Binary release
   4. Generated documentation
      1. Manually written content to wiki
      2. Javadoc / doxygen-style API docs