It's been almost a full year since my last news update. Hi!

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

After a significant number of years (since approx 2003) running PyBlosxom, willg has stepped down from managing the project and passed it over to me, Akai.
will, thank you for your considerable effort in making PyBlosxom the program we know and love today.

I'm available on the mailing lists and frequently on the IRC channel (as AkaiKitsune) for any question or issue I can help with.
Part of the handoff is the move from the bluesock.org domain to github for both the site and the repositories.
Update your bookmarks to http://pyblosxom.github.com/, that's our new home!

-Akai

This fixes two issues:

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

pip install pyblosxom

pip install --upgrade pyblosxom

This fixes two issues:

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

It's been a while since the last status update and a lot has happened since then:

• 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.

We did 1.5 rc2 10 months ago. Since then we've added a few new plugins, fixed a bunch of bugs, worked on making the documentation better, updated docstrings, and some other stuff.

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)

We've done a ton of work over the last 3 and a half months. One thing that I finally got around to was overhauling the web-site. The new web-site is (I think) a lot better, more informative, and easier to use.

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)

Development slowed down during the second half of 2010 because I was bogged down with other things. I recognize how that totally sucks for the project. I'm working on rectifying it now.

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)

It's been about 6 months since 1.5 rc1. Since then we've been updating plugins, added some new plugins, adding tests, fixed documentation, added a sortlist callback, updated docstrings, switched from subversion to git, moved from SourceForge to Bluesock, and some other stuff.

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)