It's been a pretty tumultuous year both for me and PyBlosxom.

I've spent a lot of this time getting used to the codebase, which was frankly somewhat intimidating to someone new to the project, which I was when I first joined a year ago.

On the Pyblosxom front,Although we haven't had a super-large amount of updates, We did get some bugs squashed and began a new repo for external plugins, which I hope will eventually lead to plugins being more updated and accessable

Markus Koschany (https://launchpad.net/~apoleon) has been working on the Debian repo to finally get our package there updated for the next release. (Thank you!)

We made the move over to GitHub will all our stuff and the documentation has been updated to reflect it

I'm happy to note it looks like we got a few new installs and a few new faces appeared on IRC

I hope this year brings a lot more to the table for PyBlosxom and my door is always open for comments, criticism, suggestions or help :-)

-Akai

-Akai

1. removed debug logging from pycategories
2. fixed a warning when doing pip install pyblosxom

pip install pyblosxom

pip install --upgrade pyblosxom

1. manifest was missing README.rst which hosed python setup.py install
2. the WHATSNEW page had the wrong version and date for the 1.5 release

The first is bad and worth putting out a new release. Sorry about that. Many thanks to ntoll who popped on IRC and let us know.

pip install pyblosxom

pip install --upgrade pyblosxom

Release!

It's been a long road for Pyblosxom 1.5. The first time I said that PyBlosxom 1.5 was pretty much done was in June of 2009. That turned out to be hilariously wrong and development continued for another two and a half years.

In that period of time, we switched from svn to git and put the project on Gitorious, we switched bug trackers, we had like 350 commits, we added tests, we started using a wiki, we abandoned the wiki, we renamed the project, we overhauled the documentation a few times, we added plugins, we removed plugins, we did the hokey-pokey and moved the rest of them around a few times, we moved the project to GitHub, we started using IRC more heavily, we had three release candidates, and a bunch of other things.

Was Pyblosxom 1.5 worth it? Definitely---it's a magnificent improvement over 1.4.3. I highly recommend upgrading.

For complete details of what's new in 1.5, read the WHATSNEW section of the manual. Here are some highlights:

1. We changed the name of the project to Pyblosxom. Down with camel case.
2. Plugins are now part of the package. When you upgrade Pyblosxom in the future, core plugins will automatically get upgraded, too. Plugin documentation is now part of the manual. There are some new plugins, some rewritten plugins, and a bunch of plugins have seen significant improvements.
3. pyblosxom-cmd is vastly improved. Creating a new blog is much easier than in previous versions.
4. Better crash handling. Pyblosxom now has a crash page that makes it easier to figure out why it's crashing and either fix it or tell someone the information they need to know to fix it.
5. Improved documentation.
6. Vastly cleaner code, more tests, and better project infrastructure.
7. More options for static rendering.

Yay for Pyblosxom 1.5!

pip install pyblosxom

pip install --upgrade pyblosxom

• renamed the project from PyBlosxom to Pyblosxom
• folded core plugins into the Pyblosxom core
• moved the pyblosxom repository from gitorious to github
• added new plugins, bug fixes, more tests, fixed documentation, ...

We're pretty close to a 1.5 final release. This release has been a long time coming and it'll be good to get it out. I'm hoping it'll happen in the next week.

There are still a bunch of polish things that need to be done, so we're going to do another release candidate.

Download the new version at pyblosxom-1.5rc3.tag.gz.

If you have any problems, say hi on IRC (#pyblosxom on irc.freenode.net), send an email to the pyblosxom-users mailing list, or send me an email at willg at bluesock dot org.

/will (willg at bluesock dot org)

Things that still need to be done:

1. update the plugin registry
2. update the flavour registry
3. compile the 1.5 documentation and push that to the site

There are still a series of outstanding tasks for PyBlosxom 1.5 that should get finished before we release 1.5 final. We're working on them. We could use your help!

• check PyBlosxom 1.5 in git to see if it works with your blog and plugins
• run the unit tests
• edit and update documentation
• triage and fix bugs in the 1.5 milestone in the bug tracker

We just finished up a sprint week and we're eager to finish up 1.5 and get it out. Hopefully, we'll get that done in the next week or two.

/will (willg at bluesock dot org)

Previously, we were using the SF bug tracker which sucked. Since we did much with it, it's undergone a user interface overhaul and it's better, but it's still missing features this project needs. So we stopped using it and I directed people to file bug reports by sending email to the pyblosxom-devel mailing list.

In October of 2010, we discussed issue trackers. Then I went on hiatus for a little over a month. I've returned now and set up Roundup to host PyBlosxom issues and feature requests. With help from Asheesh and the awesome folks at OpenHatch I added support for tracking milestones. I've moved all open bugs and features from the SF bug tracker to the new bug tracker.

You can find it at http://pyblosxom.bluesock.org/bugs/.

I also got through the queue of merge requests from Dieter. I really apologize for sitting on those for so long. I really appreciate the work he did on them.

I want to move ahead and get a PyBlosxom 1.5 rc3 out soon. We're still fixing problems in plugins and working on getting PyBlosxom and the core plugins to a stable state--hence the need for ongoing release candidates rather than a final release.

I want to thank Dieter for his prodding. Also, Tim, Marius, Bill, Michael, Glennie, Sean, Sebastian, and Asheesh for their participation, efforts, thoughts, and other positive energy things on #miro-hackers and the pyblosxom-devel list. I'm looking forward to the rest of 2011, cleaning up the project and making it better for everyone.

/will (willg at bluesock dot org)

Doing another release candidate because there's still a lot of work to do updating plugins, adding tests, and fixing documentation.

Download the new version at pyblosxom-1.5rc2.tag.gz.

If you have any problems, say hi on IRC (#pyblosxom on irc.freenode.net), send an email to the pyblosxom-users mailing list, or send me an email at willg at bluesock dot org.

/will (willg at bluesock dot org)