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)

We're moving from SourceForge to Bluesock. Bluesock is my own personal server where I'll have a lot more control over the site in terms of how it's built. On SourceForge we're severely limited to static pages or the various applications that they install. It's been a real pain in the ass.

Additionally, I've gone through the site and updated it to reflect our move from svn to git.

On top of that, we're ditching the SourceForge bug tracker. We don't have a bug tracker set up, though, so we're just going to wing it with the pyblosxom-devel mailing list. If it becomes necessary, we'll set up a new bug tracker.

PyBlosxom 1.5 is almost done. A handful of things have been done since the release candidate a while back. The documentation still needs another going over and parts of it need to be updated.

Hopefully all that will happen soon.

/will

There have been lots of changes in the last few months. We're finishing up PyBlosxom 1.5 and we're moving the project to different infrastructure. Let me cover these one at a time.

We did a PyBlosxom 1.5 rc1 release a couple of months ago. Since then, we've been hanging out on #pyblosxom on Freenode and fielding questions. I think it's going really well for everyone. As people bring up issues, we're fixing them or putting them on the TODO list to get fixed. Most of the problems revolve around plugin support or plugin bugs.

We've been working on updating plugins in the contributed plugins pack. We're also getting rid of the contributed plugins pack and going back to what we used to do several versions ago where we ship plugins with the PyBlosxom tarball. Plugins that are used by many users and are well supported will be located in the plugins/ directory of the tarball. We have a unit test system set up and we're adding tests for these plugins. We'll be making an effort going forward to update plugins as we update PyBlosxom core and everything should be shiny happy.

We're planning to rework the plugin registry on the site to provide an index of all the plugins out there--both those in the tarball and those maintained by other people. Work on this hasn't started, yet. I think this is a post PyBlosxom 1.5 project.

There are a handful of plugins that I want to update, add tests for, and move to the plugins/ directory to ship with the tarball. Once that happens, we'll release a 1.5 final.

In regards to the infrastructure, we're switching to git. Sebastian very kindly converted our svn repository into three git repositories that are now at http://gitorious.org/pyblosxom/. This will make development a lot easier going forward.

We're also scheming to rework the website so it's a better project website, has a better registry for plugins and flavours, and makes it easier for us to collaborate on PyBlosxom development.

That's where we're at. If you want to contribute and/or hang out, we're on #pyblosxom on Freenode and the PyBlosxom develop mailing list.

/will (willg at bluesock dot org)