Okay, here's what happened...
Doug and I swapped emails back and forth and we decided to go ahead and release 0.3.7. We've made quite a bit of changes and added a couple of cool new things and development has sorta been sitting on the backburner for the last couple of months due to work and some personal stuff.
So, I checked the SVN log and updated the CHANGELOG, made an addition to the CREDITS, updated a couple of other things, made a tarball, uploaded it to the site, made announcements here and at Freshmeat and Sourceforge, etc.
I told Doug that, "I'll setup a release after I get home from work tonight." He thought I was just making some last minute corrections, I thought he knew I was going to make a tarball and setup the releases on Freshmeat and Sourceforge.
So, I screwed up.
The good news is, the tarball I posted to the site a couple of days ago is fine. If you downloaded 0.3.7 from here on October twenty-fifth or the twenty-sixth, you got a slightly different installer and the directory structure was a little different. Doug cleaned up the md5sums, created a md5sums directory and updated the installer. That's pretty much the only differences.
Why would I embarrass myself and re-release the tarball if they're virtually the same? Because we're trying to keep the releases in-line with the development SVN repository. It's not really a big deal, it just helps, well, me mostly, maintain some consistency with the releases.
If you're one of the precious few who has been using bashblogger since the early releases, you'll know that each tarball has been radically different from each previous version because I'm learning how to do this as I go along.
My old method of versioning was, I fixed bugs or added new features to the version of bashblogger running on my system. When I got everything the way I wanted it, I copied everything to a directory, (named bashblogger), took the config and gave it generic values, or wrote a script to write a config if I was feeling rambunctious. Tossed in a favicon, a few theme directories, (until the theme directories got too big), and a print stylesheet then tarballed the thing up, versioned it and uploaded it to the site.
It's gotten a lot better.
Doug provided a whole slew of dev tools when he came on board. I'd used monotone a little bit, some anonymous CVS checkouts, but I wasn't really comfortable with versioning systems. Boy, what a difference! It's so much easier. I don't keep a text file with changes anymore and I don't have to go throught my mutt aliases to find people to add to the credits either.
When I build a new release, I pull a fresh copy from SVN, install it on a test box and pound on it for a few days. If nothing interesting breaks, that copy is the new version. Update the docs, tarball it up, upload it and propagate the releases and I'm done. It takes me longer to write the release post here on the site than it does to do a release now.
If I ever get the time, I'm gonna script the tarball release and be able to make mistakes like this much easier.
So, I've rambled again, where was I... Oh yeah, new tarball, essentially the same thing, sorry for the confusion. That's it. Thanks for coming, please drive through.
Posted by Phil McClure in Project Release on October 27, 2007