<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 8, 2015 at 9:54 AM, Levente Uzonyi <span dir="ltr"><<a href="mailto:leves@elte.hu" target="_blank">leves@elte.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, 8 Jun 2015, Bert Freudenberg wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07.06.2015, at 13:56, marcel.taeumel <<a href="mailto:Marcel.Taeumel@hpi.de" target="_blank">Marcel.Taeumel@hpi.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
At the moment, 4.5 updates to 4.6 (trunk) just fine. I was wondering how our<br>
CI server could generate a working 4.6 release image based on an older<br>
release image.<br>
<br>
However, I think there are no things running in the CI base image and thus<br>
it might just work out fine. :-)<br>
</blockquote>
<br>
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?<br>
</blockquote>
<br></div></div>
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.<br></blockquote><div><br></div><div>I think you're also implying that a release can be defined by a specific update map right? So we could have update-Squeak46.NNN.mcm and update.spur-Squeak50.NNN.mcm, which also allows supporting bug fix releases, e.g. update-Squeak461.NNN.mcm and update.spur-Squeak501.NNN.mcm. I like this.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Levente<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Bert -<br></blockquote></blockquote></div>-- <br><div class="gmail_signature">best,<div>Eliot</div></div>
</div></div>