<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Hi,</div></div><div><blockquote type="cite" class=""><div class="">On 18 May 2017, at 19:07, Waite, Dick (External) <<a href="mailto:Dick.Waite@softwareag.com" class="">Dick.Waite@softwareag.com</a>> wrote:</div></blockquote><br class="">[…]</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; direction: ltr; font-family: Tahoma; font-size: 10pt;" class="">As a DUP update from beta-n to beta-n+1 is not an official update, SUSE only support a new install from beta-n to Beta-n+1, which from my point of view seems odd. If I have the configuration I want for this virtual machine it seem logical to me that I should be able to "update"... Maybe a few words on why a beta-n to beta-n+1 is an issue, maybe others would like to know too ?<br class=""></div></div></blockquote><br class=""><div><div><div><div>Why don’t we support updating/upgrading from SLE beta-n to beta-n+x ?</div><div>Because we need the flexibility of doing important/disruptive changes to </div><div>packages, like upgrading/downgrading to different version without taking care of</div><div>supporting it.</div><div><br class=""></div><div>So for instance, we can move forward with SLE Beta-n+4 without even think about</div><div>upgrading SLE Beta-n to SLE Beta-n+4 and take care of all the changes between </div><div>these versions. At the end of the day we only care about migrating from </div><div>the previous SLE to SLE Beta-n+4.</div><div><br class=""></div><div>Changes between SLE Beta might not be like regular updates we make in official </div><div>SLE SP released. Since our customers might not face this kind of changes with </div><div>official SLE SP in production it seems useless to take extra care on supporting</div><div>this for our Beta Phase. And this allow us to focus on more important aspects</div><div>for the final version of the SLE SP we are preparing during the beta program.</div><div><br class=""></div><div>Don’t forget that support also means to dedicated QA resources (humans and </div><div>machines) for various scenarios. </div><div><br class=""></div><div>I didn't go into much details but I hope you understand our points.</div><div><br class=""></div></div></div></div></div><div><blockquote type="cite" class=""><div class=""><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; direction: ltr; font-family: Tahoma; font-size: 10pt;" class="">Anyway as you say, I can always run a supported zypper migration from SP-2 GA to each Beta and RC and GMC<br class=""><br class="">Many thanks to the team, SP-3 has gone very well to-date, lets keep the fingers crossed.</div></div></blockquote><div><br class=""></div>Great to hear, thanks!</div><div><br class=""></div><div>Have a nice day,</div><div>Regards,<br class="">-- <br class="">Vincent Moutoussamy<br class="">SUSE Beta Program and SDK Project Manager</div></body></html>