[scummvm-devel] Prepare for ScummVM 2.6.1

[Lothar Serra Mari]

Hi all,

a few weeks after the release of ScummVM 2.6.0, it is now time to 
prepare for the next maintenance release, ScummVM 2.6.1.

ScummVM 2.6.1 will evolve from the current branch-2-6 
(https://github.com/scummvm/scummvm/tree/branch-2-6)

Since the purpose of ScummVM 2.6.1 is to fix bugs that were spotted in 
the current stable release and we'll not include any new features or 
engine, we'll go with a tighter release schedule than we did for the 
previous release:

     Thursday, October 13: hard freeze of branch-2-6
     Sunday, October 16: Tagging of ScummVM 2.6.1, porters start 
building and submitting their releases
     Monday, October 31: Public release

Bugfixes should be submitted to the master branch first. Please note 
that _only_ bugfixes and _really_ important QoL improvements should be 
backported to branch-2-6. If you want to backport something that has the 
potential of even very slight regressions, please submit this as pull 
request only since we want to avoid further regressions at any costs.

A list of currently open bugs is available at 
https://bugs.scummvm.org/report/17. However, for this minor release you 
should mainly focus on smaller bugs that don't require major work on 
engine or backend code. Backporting changes within the COMMON namespace 
should be avoided.

All the best
Lothar

-- 
Lothar Serra Mari
ScummVM Co-Lead