<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=""><div class="">Hi,</div><div class=""><br class=""></div><div class="">It seems that there was already some good testing for the new games, but maybe a short testing period would not be a bad idea? That would also leave a bit more time for porters to work on their port if needed. Otherwise if we go with the short schedule, maybe it could be extended by one week with tagging on December 1st as it seems a bit tight for porters?</div><div class=""><br class=""></div><div class="">As for the version number, I don't have a strong opinion, but the addition of all those SCI games seems a good occasion to bump the major version and go with 2.0.0.</div><div class=""><br class=""></div><div class="">I can help a bit with the release process as well, but this weekend (November 11 and 12, or maybe only on the Saturday) I am planning to go to the AdventureX convention in London, so I won't have much time.</div><div class=""><br class=""></div><div class="">Thierry</div><div class=""> </div><br class=""><div><blockquote type="cite" class=""><div class="">On 7 Nov 2017, at 23:12, Colin Snover <<a href="mailto:scummvm-devel@zetafleet.com" class="">scummvm-devel@zetafleet.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">Hi,<br class="">
<br class="">
It has been a while since a release so I would lean slightly
toward the faster schedule. Dafioram has already done a lot of
testing, and as a result, things seem like they are in a good
place. Porters may need a little more time than usual to fix up
their GraphicsManager implementations since that API was changed
for this release, though I don’t know if that needs to impact the
schedule (I already emailed about this a while ago, so it’s
hopefully not news to anyone).<br class="">
<br class="">
I would like to get optimised builds in the hands of others to
verify whether anything more needs to be done for
<a class="moz-txt-link-rfc2396E" href="https://bugs.scummvm.org/ticket/10248"><https://bugs.scummvm.org/ticket/10248></a> (this is one of the
reasons I have been working on Buildbot lately). Testing locally I
think that normal compiler optimisations solve the problem, and it
would be nice to have others verify this too. In any case it
doesn’t block a release since there are already mitigations in
place (the configurable audio buffer size) that end-users can
apply if needed.<br class="">
<br class="">
For the release process, I will assist on reviewing open tickets
and communicate on IRC about this to coordinate.<br class="">
<br class="">
With regards to versioning, that’s a can of worms! Since ScummVM
isn’t a library that needs to communicate API compatibility,
semver doesn’t really apply here, so to me it would seem
appropriate to use some other versioning system like year.month,
or just major.patch, for simplicity. But I have no strong opinion
in any case, so would encourage anyone that has a stronger opinion
to say why.<br class="">
<br class="">
Best,<br class="">
<br class="">
On 2017-11-07 01:22, Eugene Sandulenko wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAJG28-aj11nuEq53CUUFC0gxt5YaS8bOf1dPz1Maee+L10TAkg@mail.gmail.com" class="">
<div dir="ltr" class="">Hi Team,
<div class=""><br class="">
</div>
<div class="">Now, both SCI3 and Starship Titanic bugfixing is mainly
over, thus I'd like to propose to launch the 1.10.0. Maybe we
should call it 2.0.0?</div>
<div class=""><br class="">
</div>
<div class="">I am not sure we can get enough testers at this time, but
I'm leaving it open, and propose two schedules: with and
without the extensive testing period.</div>
<div class=""><br class="">
</div>
<div class="">With testing:</div>
<div class=""><br class="">
</div>
<div class="">November 12: Release cycle starts, testing announced, list
of bugs published. Trunk is frozen</div>
<div class="">November 19: branch, trunk unfrozen, porters contacted</div>
<div class="">December 8, Fri: tagging, tarballs uploaded, porters start
submitting their builds</div>
<div class="">December 17: Release</div>
<div class=""><br class="">
</div>
<div class="">Without testing:</div>
<div class=""><br class="">
</div>
<div class="">November 12: branch, list of critical bugs published,
porters contacted</div>
<div class="">November 24, Fri: tagging, tarballs uploaded, porters start
submitting their builds<br class="">
</div>
<div class="">December 3: Release</div>
<div class=""><br class="">
</div>
<div class="">Which schedule to choose? If we chose without testing, then
I anticipate 1.10.1 (2.0.1?) in mid-January and perhaps .2 in
February/March.</div>
<div class=""><br class="">
</div>
<div class="">What about the version number? Should we switch to 2.0.0
since all SCUMM and SCI games are supported?</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Eugene</div>
<div class=""><br class="">
</div>
<div class=""> </div>
<div class=""><br class="">
</div>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
Scummvm-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Scummvm-devel@lists.scummvm.org">Scummvm-devel@lists.scummvm.org</a>
<a class="moz-txt-link-freetext" href="http://lists.scummvm.org/listinfo/scummvm-devel">http://lists.scummvm.org/listinfo/scummvm-devel</a>
</pre>
</blockquote><p class=""><br class="">
</p>
<pre class="moz-signature" cols="72">--
Colin Snover
<a class="moz-txt-link-freetext" href="https://zetafleet.com/">https://zetafleet.com</a></pre>
</div>
_______________________________________________<br class="">Scummvm-devel mailing list<br class=""><a href="mailto:Scummvm-devel@lists.scummvm.org" class="">Scummvm-devel@lists.scummvm.org</a><br class="">http://lists.scummvm.org/listinfo/scummvm-devel<br class=""></div></blockquote></div><br class=""></body></html>