Closed cuavas closed 9 months ago
MAME 0.262 Will Have Soul Edge Version II Japanese Version And Will Fix Darius II And Sagaia SSG Sound Innacurcies Please Also Namco System 11 Have Working Graphics Also With SNK Hyper Neo Geo 64 With Perfect Sound And Graphics And Also With System 12
And Capcom Sony ZN1 And ZN2
hey we need taito g net fx 1 a and b need fix for impefect graphics and sound also with snk's hyper neo geo 64 and namco system 11 and 12 and also with capcom sony zn-1 and zn-2 and inaccurate sound emulation on darius ii and sagaia also with support for japanese version of sagaia also soul edge version ii japanese version support please fix me with new version of mame please
konami system 573 network is it gonna work or what
i would wait to see that
and also support for soul edge version ii japanese version as well as sagaia japanese version as well please
Create release branch
master
branch, and runmake cleansrc
git diff -b
as well asgit diff
to see changes that affect things other than whitespace)DEBUG=1 TOOLS=1
to ensure changes compile/validatefor x in hash/*.xml ; do xmllint --noout --valid "$x" ; done
for x in hash/*.hsi ; do xmllint --noout "$x" ; done
master
branchmaster
branch on GitLab and SourceForgeRun 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:tiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargetFor the following configurations, ensure a build compiles, links and validates, and basic functionality works:
tiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargetFor the following configurations, ensure a build compiles, links and validates,
-listxml
output validates, minimaws ORM check passes, and basic functionality works:tiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargettiny
subtargetvirtual
subtargetFor the following configurations, ensure a build compiles:
Generate preliminary release notes
mame
repository and latestmaster
branch frombuild
repositorybuild
repository, run script to scrape commits and pull requests, e.g.python3 makewn.py -c ../mame -u <user> -o whatsnew/whatsnew_0124.txt
-listxml
output from previous release from a download mirror-listxml
output with a preliminary build from the release branchbuild
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
Prepare release notes
language
folder and list updated translation in the relevant section at the topmaster
branch, and let people know it’s ready for proof-readingBuild release
build
repository, scrape latest commits, do a final check of release notes, commit changes, and push tomaster
branchandroid-project/app/src/main/AndroidManifest.xml
(two lines),docs/source/conf.py
(two lines), andmakefile
(two lines)git tag -s -m"MAME 0.124" mame0124
mame
repository into a clean directory and check out release tag, e.g.git clone -b mame0124 mame mame-release
git describe
andgit log -1
show what’s expectedbuild-release.bat
inbuild
repository to build 64-bit release binaries, e.g.(MINGW64=/mingw64 MINGW32= make TARGET=mame TOOLS=1 SEPARATE_BIN=1 PTR64=1 OPTIMIZE=3 SYMBOLS=1 SYMLEVEL=1 REGENIE=1 -j9 ARCHOPTS="-fomit-frame-pointer -fuse-ld=lld" OVERRIDE_AR=llvm-ar && make -f dist.mak PTR64=1 -j5) |& tee ../build64.log
build
repository is up-to-daterelease.sh
frombuild
repository to package release, e.g.bash ../build/release.sh 0124
Prepare media
oldrel.php
releases
folderposts
<!--more-->
tag, adding HTML markup for formatting<tt>
formatting for literal code, command-line options, etc.<!--more-->
tag – aim for at least three paragraphs of content, call out a few interesting or notable changesUpload assets for release
master
branch on GitLab and SourceForgemaster
branch from GitHub, merge release tag, and push tomaster
branch on GitHub7za t
to test integrity of downloaded archivessha1sum -c < SHA1SUMS
andsha256sum -c < SHA256SUMS
TZ=utc touch -t 201909040000 0.213/* 0.213
rsync -avzhc --progress -e ssh 0.124 frs.sf.net:/home/frs/project/mame/mame/
Publish release
master
branch and wait for static pages to be regeneratedscripts/xslt/list-system-sources.xslt
to generate the list)