Release FunFX

These instructions are only for FunFX developers. If you’re not an administrator of the RubyForge FunFX project, you will get permission denied for this.

Before the release

• All specs should be passing
• Make sure History.txt lists all significant changes for this release
• Make sure you have closed all fixed issues in Lighthouse
• There should be no pending commits to your local repository

Releasing the gem, tgz and swc

This is done with the release task that comes with Hoe. After you have configured Hoe you can upload a gem to RubyForge with one command (standing in the release directory):

rake release VERSION=x.y.z

Replace x.y.z with the version inside the lib/funfx/version.rb file.

Uploading the swc to the Maven repository

In order to make builds easier for people who build their Flex code with Maven, we’re hosting a separate maven repository on RubyForge that contains the various versions of FunFX.swc.

When you have released the gem, upload the FunFX.swc like this: TODO – WRITE ME

TODO – make this part of the release task so it doesn’t have to be a separate step.

After a release

• Bump the version in lib/funfx/version.rb
• Bump the version in flex/build.sh, flex/build.bat, demo-app/build.sh and demo-app/build.bat
• Add a new section to History.txt
• Commit and push
• Wait a few hours for the gems to rsync to mirrors
• When you can gem install funfx and get the latest version, send an announce email to the mailing list.