On Mon, 8 Jun 2015, Bert Freudenberg wrote:

> On 07.06.2015, at 13:56, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:
>>
>> At the moment, 4.5 updates to 4.6 (trunk) just fine. I was wondering how our
>> CI server could generate a working 4.6 release image based on an older
>> release image.
>>
>> However, I think there are no things running in the CI base image and thus
>> it might just work out fine. :-)
>
> We’ve never tried supporting a direct upgrade between releases. If someone wants to spend time on that then fine, but the only disadvantage of doing it via trunk updates is that it runs for a bit longer, right?

One of the easiest way to add this feature is to let the update process 
stop at a given .mcm, and tag some .mcms as releases. That way we can use 
the Trunk repository to upgrade from one release to another.

Levente

>
> - Bert -
>
>
>
>