[Scummvm-devel] ScummVM 1.3.1 release tarballs are up

[Oystein Eftevaag]

40766a3cca8cd967266bf15542f5f2d1  scummvm-1.3.1-iphone.deb
94ac6394a4911daef45f8d4844bb6c18  scummvm-1.3.1-macosx.dmg

// Oystein

On 03.07.11 17.26, Eugene Sandulenko wrote:
> Hi Team,
>
> ScummVM 1.3.1 was "tagged". No tools update this time:
>
> 32cbfbd916f16892030dcc5a7ac6d5f0  scummvm-1.3.1.tar.bz2
> f91220d7fbcd10e28e08bc9e19550dc7  scummvm-1.3.1.tar.gz
> dab01142f0faae8873783675f74c39d5  scummvm-1.3.1.zip
>
> The tarballs are created from branch-1-3-1, commit
> 3998a9e36417e40c5640cf301fdbd61890c08d49. Please denote the config
> hash, as the branch occasionally may go forward, in case we retag
> (hope we will not).
>
> Now porters should upload their binaries to the FRS before July 12th
> (Tuesday), our release date. Please make sure to follow the file
> naming conventions as described on
> <http://wiki.scummvm.org/index.php/HOWTO-Release#Binaries>.
>
> Also let me remind that it is essential to use --enable-release
> configure flag for your builds.
>
> The easies way to upload port binaries is via SFTP, described here:
>
> <https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download>
>
> Upload directory is:
>
> /home/frs/project/s/sc/scummvm/scummvm/1.3.1
>
> Please upload your tarballs ASAP.
>
>
> Eugene
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Scummvm-devel mailing list
> Scummvm-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scummvm-devel