Cannot create a release because a newer release already exists (v3.6.5)

[Guest]

Dear support,

Within our organization we use a release schema of YYWW, for example 1403, 1404, etc.
This is related to the sprints we have every 2 weeks.
So, at this moment we have the release 1412 in production.

Last monday, we started the new sprint, named 1413.
The deployment consists of 3 different applications.
All was working well, up to now.

One of the applications was craching so an emerency fix was needed.
In stead of having an emercency deployment plan, the release was cancelled.
The new releasenumber was set to ... "141201".
The intention was to identify the first "01" sub-release of "1412".

Of course this worked, but now we have the problems generating the new releases.

For this specific application, the release "1413" can not be un-cancelled, because of the newer release.

Can you give us a hint to regenerate our scheme and reactivate "1413".

Kind regards
Martin van Berkel

Product: BuildMaster
Version: 3.6.5

[Guest]

Unfortunately that is a limitation of the v3.X line of BuildMaster - releases were ordered and meant to be built on top of each other, e.g. once version 5 goes out, it is meant to encompass everything up through v5.

If you were to upgrade to the 4.X line (make sure to read all the upgrade notes first), then you can actually re-order releases as necessary, and allow other advanced workflow options.