Release: MAME 0.252

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.260

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.257

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.256

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.253

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.254

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.263

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.261

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.258

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.251

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.264

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.265

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.262

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.259

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Release: MAME 0.250

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

Build release

Prepare media

Upload assets for release

Publish release

Mark current version as released on MAME Testers, and update with actual release date
Publish release on GitHub
Push web site changes to master branch and wait for static pages to be regenerated
Check HTML and RSS pages, ensure a few links work
Create forum threads on forum.mamedev.org, forums.bannister.org, and mameworld.info
Create reddit posts on r/MAME, r/emulation and r/cade
Create a new, pinned GitHub Discussion in the Announcements category, and unpin the previous release announcement discussion
Update version number in topic on #mame on Libera IRC
Update system driver source file list on MAME Testers (use scripts/xslt/list-system-sources.xslt to generate the list)

Release: MAME 0.255

Create release branch

Pull latest master branch, and run make cleansrc
Check differences, manually clean up anything broken (useful to check git diff -b as well as git diff to see changes that affect things other than whitespace)
Do a full build with DEBUG=1 TOOLS=1 to ensure changes compile/validate
Check software lists against DTD: for x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
Check software hash files’ XML structure: for x in hash/*.hsi ; do xmllint --noout "$x" ; done
Commit changes and push to master branch
Create release branch and push to GitHub
Push branch point to master branch on GitLab and SourceForge
Create new version on MAME Testers with anticipated release date (last Wednesday of following month, 00:00:00Z), marked unreleased

Run build matrix

In addition to the basic coverage provided by GitHub Actions, MAME needs to be built and tested across a representative spectrum of configurations.

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, and basic functionality works:

For the following configurations, ensure a build compiles, links and validates, -listxml output validates, minimaws ORM check passes, and basic functionality works:

For the following configurations, ensure a build compiles:

i686, Linux, GCC, libstdc++, debug, with tools
i686, Linux, GCC, libstdc++, non-debug, with tools

Generate preliminary release notes

Pull latest release branch from mame repository and latest master branch from build repository
In build repository, run script to scrape commits and pull requests, e.g. python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
Get -listxml output from previous release from a download mirror
Generate -listxml output with a preliminary build from the release branch
In build repository, run script to identify added/promoted/renamed/removed machines, e.g. python3 newdrivers.py mame0123.xml new.xml | tee -a whatsnew/whatsnew_0124.txt
Copy resolved bugs from MAME Testers change log page to relevant section in release notes
Before any editing, commit generated release notes for reference

Prepare release notes

Reconcile added/promoted systems and software with credits in commit messages and pull request descriptions, moving entries to the relevant sections at the top, and sorting correctly
Check commit log for language folder and list updated translation in the relevant section at the top
Sort resolved bugs and edit descriptions
Summarise merged pull requests, making verb tense consistent
Standardise contributor names
Strategically use non-breaking spaces to hopefully avoid line breaks at inopportune points
Add anticipated release date to top line
Commit changes, push to master branch, and let people know it’s ready for proof-reading

mamedev / build Goto Github PK

build's People

Contributors

Stargazers

Watchers

Forkers

build's Issues

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch

Run build matrix

Generate preliminary release notes

Prepare release notes

Build release

Prepare media

Upload assets for release

Publish release

Create release branch