As of version 1.0, the release mangement process of PloneSoftwareCenter has changed slightly from previous iterations. Please follow these guidelines:

Add releases numbered as they will be in the final release. When you begin work on what will become MyGreatProduct 1.1, create a release numbered 1.1. The title of the release will initially be "MyGreatProduct 1.1 (Pre-release)". This release will start in the "pre-release" state.

When you are ready to make an alpha, beta, release candidate or final release, use the state drop-down to make such a release. The title of the release will change, e.g. to "MyGreatProduct 1.1 (Alpha release)". Note that the state is not applied to final releases (i.e. you do not see "MyGreatProduct 1.1. (Final release)").

If you release a second alpha/beta/release candidate, select re-release from the state drop-down. This will automatically increment and add a release number. The title will change to "MyGreatProduct 1.1 (Alpha release 2)". Again, the number is dropped for the first alpha/beta/release candidate, and only shown starting from 2. If you re-release again, the number will be incremented so that you get "MyGreatProduct 1.1 (Alpha release 3)". If the numbering gets out of sync, you can go to the edit tab and edit it. Clearing the field will turn automatic numbering off.

To make a different kind of release, e.g. a beta to follow your alpha, select release beta from the state drop-down. The release number counter will be reset to 1 (and the number hidden for the first beta).

The normal procedure when updating a release between maturities is to delete the redundant files. For instance, when changing an alpha to a beta you would get rid of the alpha release files. This is of course up to you, but we recommend it to minimize confusion on what to download.