AMSN Release Guide

1. Create a new branch for the release
2. svn copy amsn from trunk to branch directory
3. Update credits in README, in case someone is missing (in branch)
4. Update Changelog/TODO file (and maybe Wiki too) (in branch)
5. Update $version, $date, $rcversion variables at the beginning of "amsn" file. (in branch)
6. Inside configure.ac, update APPSTABLE from no to yes and change versiion. (in branch)
7. Edit autopackage version
8. Do an autoconf (in branch)
9. Make sure the binaries for TkCximage? and Webcamsn, for Windows (DLL) and Mac OS X (.dylib) are updated (in branch)
10. Commit all changes to the branch
11. Make sure language maintainers had a one week notice to translate everyhing and tell them the official deadline.
12. Make sure all pending languages are processed.
13. Create a tag directory for the version
14. svn copy amsn from branch to tag directory
15. Do a: cvs export msn to have a clean copy of the CVS (without CVS/ folders or extra files)
16. Do a: cvs export amsn-extras to get some additional skins
17. Add shipped skins (at the moment, default one, and Tux) from amsn-extras to skins/.
18. Test everything runs fine
19. Tar-gzip the msn/ folder, removing any unnecessary extras. (Shouldn't be any). As some kind of "standard" in the gnu world, if the tar.gz is amsn-0.93.tar.gz, the folder inside must be called amsn-0.93.
20. Ask packagers to create amsn packages:
21. Upload file to ftp://upload.sourceforge.net/incoming (user: anonymous)
22. Add a new file release in the SourceForge File Release System
23. Wait for Sourceforge mirrors to get synced
24. Edit Downloads using AdminDownloads module in our web page to update download links, and add a piece of news.
25. Edit "amsn_latest" file in htdocs/ to update version for automatic version checking feature
26. Update plugins in AdminPlugins
27. Add some news to SF news, freshmeat, slashdot, The Times...
28. Update information on wikipedia

---

Official packages

Mac OS X package
Tom Hennigam

---

Autopackage i386:
Phil

---

Autopackage x64:

---

Windows installer, by NSIS:
Phil

Unofficial packages

Gentoo Ebuild:
Boris Faure

---

Fedora Core Package
Sander Hoentjen

---

Debian package, official Debian Sid packager:
Søren Boll Overgaard <bilbo at debian.org>

---

NoTes from Phil for packaging

AMSN Release Guide

1. Update credits in README, in case someone is missing
2. Update Changelog/TODO file (and maybe Wiki too)
3. Update $version and $date variables at the beginning of "amsn" file.
4. Commit all this changes to CVS
5. Add a tag on CVS for this stable version (like "Release-0_9x")
6. Do a: cvs export msn to have a clean copy of the CVS (without CVS/ folders or extra files)
7. Do a: cvs export amsn-extras to get some additional skins
8. Add shipped skins (at the moment, default one, and Tux) from amsn-extras to skins/.
9. Test everything runs fine
10. Tar-gzip the msn/ folder, removing any unnecessary extras. (Shouldn't be any). As some kind of "standard" in the gnu world, if the tar.gz is amsn-0.93.tar.gz, the folder inside must be called amsn-0.93.
11. Upload file to ftp://upload.sourceforge.net/incoming (user: anonymous)
12. Add a new file release in the SourceForge File Release System
13. Edit Downloads using AdminDownloads module in our web page to update download links, and add a piece of news.
14. Edit "amsn_latest" file in htdocs/ to update version for automatic version checking feature
15. Add some news to SF news, freshmeat, slashdot, The Times...
16. Ask packagers to create amsn packages:
    • Linux installer, by bitrock: Daniel Lopez <daniel at bitrock.com>
    • Windows installer, by badlop: Badlop <badlop at ono.com>
    • RPM package, by Jasper <jasper at schoolzuigt.nl>
    • Suse package, by Guillermo Ballester Valor <gbv at oxixares.com>
    • Debian package, official Debian Sid packager, Søren Boll Overgaard <bilbo at debian.org>
    • Slackware package, by VampireWolf: Daniel Lopez <evilgeniusempire at hotmail.com>
    • Mac OS X package, by Jerome Gagnon-Voyer(Germinator) <germinator2000@users.sourceforge.net>