Here are some more alpha builds. These should have the 404 problems people have been reporting taken care of.
Source tarballs:
http://www.davefancella.com/armagetrona ... rc.tar.bz2
http://www.davefancella.com/armagetrona ... src.tar.gz
Autopackages for Linux:
http://www.davefancella.com/armagetrona ... nu.package
http://www.davefancella.com/armagetrona ... nu.package
So, how I intend to release.
We'll do at least one more alpha that will be a dress rehearsal of this process.
Basically, what we're doing is putting up packages to make sure they have everything they're supposed to have and don't have any obvious bugs that would prevent them from being good test subjects. For the most part, it's reasonably stable (although not stable at all compared to 0.2.
. But there always seem to be a few things that are wrong right when we start trying to build packages, so the alphas are to work out those problems.
So, we need at least one alpha for windows and mac os x before we do the dress rehearsal. If we need more for each, we'll do them.
When it's time to release, I will initiate the release by putting together the source tarball and uploading it to sourceforge and aabeta. I'll also knock out the autopackages at that time. Whoever is going to build the release for Windows and Mac OS X needs to build from the tarball, *not* from bzr sources. Bzr sources will still be tagged so we can reconstruct the release if we need to, but will be merged back to the trunk and the branch abandoned as soon as the source release has been made.
The windows and mac os x packages should be built and uploaded asap to aabeta. If you don't have the necessary permissions in the project to put your build on sourceforge, just let me know it's there and I'll take care of it.
So, for you who are building windows and/or os x packages, you should get the 0.3.1 branch at the tag "0.3.1_alpha2" and build a quick package and post it here for testing. If you have problems with the package that haven't yet been discovered, go ahead and update to the latest in the branch to make your changes and be ready for the next alpha. You're free to release unmarked snapshots on your own schedule for testing, of course.