#SCUMMVM BLOODNET FILES NEEDED UPDATE#
#SCUMMVM BLOODNET FILES NEEDED CODE#

Use make translations-dat to update the translations data file (and then commit it if it was changed).For a major release, make sure the translations.dat file is up to date.Browse 'git log' since the previous release and add all significant changes to the NEWS file.

Get people to do lots of testing, possibly by asking for help via a news item.Get even more people to fix all the other bugs, if possible :-).Identify other important bugs and get people to fix them.Identify release critical (show stopper) bugs and get people to fix them.Ensure ADGF_TESTING/ADGF_UNSTABLE flags are correct for the release.Run make release-checks for performing several routine checks covered below:.Update IRC and Discord channel description.Login on Buildbot, force a build of fetch-stable with cleaning and packaging to create packages for the new stable.Remove the old snapshots: rm /home/buildbot/dockerized-bb/buildbot-data/packages/snapshots/stable/*.

#SCUMMVM BLOODNET FILES NEEDED CODE#

Update the code on the server and reload the buildbot as described here.

Edit the file platforms.py and remove all specific rules mentioning ScummVMStableBuild.

Remove the customizations in class ScummVMStableBuild if there were any to make the code inherit from ScummVMBuild without any difference.

Edit at the end of builds.py the line starting with builds.append(ScummVMStableBuild('stable'.

Set the color to Warning, set the expiry date to the translation freeze date, and make sure the Notify users option is toggled on. You have until Thursday December 14 to update your translations.

Post an announcement along the line of ScummVM 2.8.0 will be released soon.

Go to the announcement settings for the ScummVM/scummvm component on the translations website:.

Change the Repository branch setting from master to the new branch.

Go to the component Version control Settings:.

git push origin tag desc/2.8.0git master.

Create annotated tag desc/2.7.0git on that commit and push.

git commit -m 'RELEASE: This is 2.8.0git' -a.

Increase version on master to 2.8.0git, and commit.

git commit -m 'DOC: Update iOS clone command for 2.6 branch'.

git add doc/docportal/other_platforms/ios_build.rst.

Change git clone to git clone -depth 1 -b branch-2-7.

Update doc/docportal/other_platforms/ios_build.rst to clone the new branch.

git push origin tag desc/2.7.0pre branch-2-7:branch-2-7.

Create annotated tag desc/2.7.0pre on that commit and push.

git commit -m 'RELEASE: This is 2.7.0pre' -a.

Increase version on branch-2-7 to 2.7.0pre (using devtools/ see below), and commit.

Create a branch for the 2.7.x releases from master, named branch-2-7.

Go to repository maintenance for the ScummVM/scummvm component on the translations website:.

Before creating the branch make sure there is no pending changes on weblate.

Watch for any potential blockers and pat developers who own the identified blockers.

Normally, we collect playtests on the forums

Track daily testing progress and update Wiki if applicable.

Share those e-mails in the release discussions thread on Discord.

E-mail the scummvm-devel list at least weekly with the list of release blockers and nice-to-have-fixed bugs.

Create a thread in the #team-talk channel on Discord: 'X.Y.Z Release Preparations' for easier communication.

Announce the testing period on the main website and copy to the forums and FB.

If some games must be fixed before the release, identify those and create a list at Release Testing.

Update the lists of files below, adding new engine data files and such.

Look through all the open issues on the bugtracker and identify release blockers and nice-to-have-fixed bugs.

e-mail -devel with the proposed schedule, ask if someone would like to finish some functionality.

September 17 (Fri): Release tagged, porters asked to submit their builds

For reference, ScummVM 2.3.0 was built according to the following schedule:Īugust 14 (Sat): Release testing announced, feature freeze in masterĪugust 28 (Sat): Release branch created, master unfrozen.

Make the release plan, normally 1-2 weeks before branching, 3-4 weeks for bug fixing, 2 weeks after tagging before the release.

Minor release: A minor release marks the exact version we release, e.g.

Major release: A major release marks the leap from e.g.

14 Generating the Icons and Shader packs.

Scummvm bloodnet files needed