Build a release

---

• [major] tasks applies on x or x.y releases only like 2.0 or 1.7
• [minor] applies to x.y.z fix releases like 1.6.7
• [RC] applies to release candidates

---

Contents 1 Legals 2 Code 3 SourceForge 4 Web site 5 Ticket manager 6 Others 7 New major release setup

Legals

[major]

• Update Dependencies and Derivated website pages
• Paste these two pages into src/legals/ txt files

Code

Note : we assume that we are about to release branches created using git-flow^[1].

• [all] Refresh workspace
• [all] Commit and push all changes in jajuk project
• [all] Check stashed code

git stash list
git stash show -p stash@{<n>}

• [major] Cleanup code (imports, formating, jautodoc and clean-up)
• [minor,major] Search for debug System.out (15 regular so far)
• [major] Detect and drop useless labels from every langpack (jajuk.properties files)
• [major] Update dependencies files in code and on the website
• [major] Change README notes version in src/doc/README.html
• [all] In build.xml and pom.xml of the hotfix[minor] or the release[major] branch, bump version :
  • Right version.
  • [RC] uses a name like x.z~RCz, see #1735
  • Change version in pom.xml (remove the "-SNAPSHOT")
  • [major]

git-flow release finish release-x_y

• • [minor]

git-flow hotfix finish release-x_y

• • [minor,major] Update the src/packaging/pad/jajuk_pad.xml file (date + version:+ exe url; 5 lines to change). Change URL inside the pad file, use http://repository.jajuk.info.
  • Commit all that stuff

git commit -a -m "Bump version for release x.y.z"

• • Launch the build from the CI server
• [all] Test it a minima under several OS
• [all] Push tags

git push origin --tags

1. ↑ http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/

SourceForge

• [all] Release on SF
  • Add files (6 files) from jajuk server :

cd /tmp/jajuk-dist/packages
sftp bflorat,jajuk@frs.sourceforge.net
cd  /home/pfs/project/j/ja/jajuk/jajuk/
mkdir <release>
cd <release>
put *
exit

• • Change default OS for each SF file at http://sourceforge.net/projects/jajuk/files/jajuk/
• [major] Backup SF data
  • Backup mailing lists; https://lists.sourceforge.net/mbox/jajuk-developers
  • Backup SF data : https://sourceforge.net/export/xml_export2.php?group_id=91412
  • Backup java installer
• [minor,major] Create a SF news

Web site

• [major] Create a README page : http://jajuk.info/index.php/Release_notes_x.y
• [minor,major] Change Download and Main page
• [minor,major] Check website (links, pages...)
• [all] Check JNLP distribution from the Try Jajuk Live page.
• [major] Create an wiki icon page

Ticket manager

• [all] Close bugs, known issues and Features
• [all] Check out Trac Administration to fix versions and milestones numbers.

Others

• [all] Make annonce on Twitter
• [minor,major] Make announces :
  • On http://freshmeat.net
• [all] Send a message in the developer list
• [major] If mplayer binary changed
  • update file on jajuk.info server at /var/www/repository.jajuk.info
  • Update the urls in build.xml / "Download_mplayer" target
• [major] If default_webradios.xml list changed, update file at http://svn2.assembla.com/svn/common-jukebox/common-jukebox/src/main/resources/preset_radios.xml

New major release setup

[major]

See Prepare a new release environment