ScummVM 2.1.0 release: branched

--===============5560564008038764775==
Content-Type: multipart/alternative; boundary="000000000000a8bada05932bca66"

--000000000000a8bada05932bca66
Content-Type: text/plain; charset="UTF-8"

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

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

<div dir=3D"ltr">Hi Team,<div><br></div><div>I just branched=C2=A02.1.0. Th=
at means, that from now on, all critical commits, particularly those, fixin=
g the bugs, will need to be backported.</div><div><br></div><div>How to bac=
kport:</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 t=
hat everything compiles</div><div>=C2=A0 6. Push</div><div><br></div><div>T=
he remaining schedule is:</div><div><br></div><div><div>22 Sept, Sun: Branc=
h, from now on all the bugfixes must be backported. Porters start to test t=
heir builds</div><div>4 Oct, Fri: Tagging. Porters start to submit their bu=
ilds</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 getting many tes=
ters, or at least, people are not reporting their progress.</div><div><br><=
/div><div>There are few bugreports for the new engines, however, please reg=
ularly check those.</div><div><br></div><div><br></div><div>Eugene</div><di=
v><br></div></div>

--000000000000a8bada05932bca66--


--===============5560564008038764775==
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

--===============5560564008038764775==--