Re: ScummVM 2.1.0 release: branched

--===============0050982698009152163==
Content-Type: multipart/alternative; boundary="0000000000003650f205934e385f"

--0000000000003650f205934e385f
Content-Type: text/plain; charset="UTF-8"

Cool! I'll try to give it a look over on Haiku in the coming period.

Luc

Op ma 23 sep. 2019 om 00:26 schreef Eugene Sandulenko <[email protected]>:

> Hi Team,
>
> I just branched 2.1.0. That means, that from now on, all critical commits,
> particularly those, fixing the bugs, will need to be backported.
>
> How to backport:
>   1. Commit to master
>   2. Check that everything is fine
>   3. Switch to branch-2-1
>   4. git cherry-pick your commits from master
>   5. Check that everything compiles
>   6. Push
>
> The remaining schedule is:
>
> 22 Sept, Sun: Branch, from now on all the bugfixes must be backported.
> Porters start to test their builds
> 4 Oct, Fri: Tagging. Porters start to submit their builds
> 13 Oct, Sun: Release
>
> I am not publishing the list of bugs, as the team size is relatively
> small, and the code quality is pretty good. Just as expected, we are not
> getting many testers, or at least, people are not reporting their progress.
>
> There are few bugreports for the new engines, however, please regularly
> check those.
>
>
> Eugene
>
> _______________________________________________
> Scummvm-devel mailing list
> [email protected]
> https://lists.scummvm.org/listinfo/scummvm-devel
>

--0000000000003650f205934e385f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Cool! I&#39;ll try to give it a look over on Haiku in=
 the coming period. <br></div><div><br></div><div>Luc<br></div></div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Op ma 23 sep=
. 2019 om 00:26 schreef Eugene Sandulenko &lt;<a href=3D"mailto:sev@scummvm=
.org">[email protected]</a>&gt;:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr">Hi Team,<div><br></div><div>I just branched=
=C2=A02.1.0. That means, that from now on, all critical commits, particular=
ly those, fixing the bugs, will need to be backported.</div><div><br></div>=
<div>How to backport:</div><div>=C2=A0 1. Commit to master</div><div>=C2=A0=
 2. Check that everything is fine</div><div>=C2=A0 3. Switch to branch-2-1<=
/div><div>=C2=A0 4. git cherry-pick your commits from master</div><div>=C2=
=A0 5. Check that everything compiles</div><div>=C2=A0 6. Push</div><div><b=
r></div><div>The remaining schedule is:</div><div><br></div><div><div>22 Se=
pt, Sun: Branch, from now on all the bugfixes must be backported. Porters s=
tart to test their builds</div><div>4 Oct, Fri: Tagging. Porters start to s=
ubmit their builds</div><div>13 Oct, Sun: Release</div></div><div><br></div=
><div>I am not publishing the list of bugs, as the team size is relatively =
small, and the code quality is pretty good. Just as expected, we are not ge=
tting many testers, or at least, people are not reporting their progress.</=
div><div><br></div><div>There are few bugreports for the new engines, howev=
er, please regularly check those.</div><div><br></div><div><br></div><div>E=
ugene</div><div><br></div></div>
_______________________________________________<br>
Scummvm-devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Scummv=
[email protected]</a><br>
<a href=3D"https://lists.scummvm.org/listinfo/scummvm-devel" rel=3D"norefer=
rer" target=3D"_blank">https://lists.scummvm.org/listinfo/scummvm-devel</a>=
<br>
</blockquote></div>

--0000000000003650f205934e385f--


--===============0050982698009152163==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Scummvm-devel mailing list
[email protected]
https://lists.scummvm.org/listinfo/scummvm-devel

--===============0050982698009152163==--