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)

It's been two years since the last release. Since then the world has turned, tools have improved (thank you Sphinx!), and PyBlosxom has undergone a lot of changes. The list of changes is really long. As such, this is a release candidate to get some more testing.

Download here:

https://sourceforge.net/projects/pyblosxom/files/

If you have any problems, please toss a bug in the bug tracker, say hi on IRC (#pyblosxom on irc.freenode.net), or send an email to the pyblosxom-users mailing list.

/will (willhelm at users dot sourceforge dot net)

I'm finishing up work on PyBlosxom 1.5. Generally speaking, development is done. Things left to do:

• documentation
• testing

Lots of cleanup, some new features (exposed commandline for plugins, truncate callback, ...), simplified startup, and some other things.

At this point, I think it's solid enough to use and I switched my blog to use it. If you're so inclined, grab it from svn, read the UPGRADE, CHANGELOG, and INSTALL documents and that should get you up and running. Some plugins might need fixing, but it works on my blog and I used it to statically compile this site.

If you have problems with PyBlosxom or with plugins, let us know on #pyblosxom on irc.freenode.net or on the pyblosxom-devel mailing list.

I re-worked the web-site so that it's checked into SVN along with the code and it's generated using the static renderer. I did this for a couple of reasons:

1. the web-site, except the wiki, is already static because we have read-only permissions to the file system on SourceForge
2. putting it in SVN allows enterprising individuals to pull the whole thing down and work to make it look way better
3. it makes it easier for us to move the PyBlosxom project to some other system
4. it provides me a really solid testing ground for static rendering

If you bump into any issues, let me know.

If you want to help overhaul the site so that it's way better, let me know.

/will (willhelm at users dot sourceforge dot net)

This release fixes some minor issues with WSGI and Paste support. It also supports template variables in the form of $(foo) which prevents variable name ambiguity. Additionally there are some bug fixes and more unit tests.

Download here:

http://sourceforge.net/project/showfiles.php?group_id=67445&package_id=65802&release_id=567698

If you have any problems, please toss a bug in the bug tracker, say hi on IRC (#pyblosxom on irc.freenode.net), or send an email to the pyblosxom-users mailing list.

/will (willhelm at users dot sourceforge dot net)

PyBlosxom is participating under the PSF in Google Highly Open Participation and it's been a huge help for our project.

In the first week, PyBlosxom had four tasks all focused on testing plugins in the PyBlosxom registry with PyBlosxom 1.4.2, reporting/fixing issues, adding documentation, ... From that we've updated five plugin entries:

• pygallery
• contact
• filter
• autoping
• latest

Many thanks to darkmessenger and CanadaBear for their work!

There are two plugin-status related tasks left in GHOP (both expired today) and four new tasks focusing on performance testing PyBlosxom and writing code in the wake of changes for PyBlosxom 2.0.

Ryan and I are writing up a task for continued work on unit tests in PyBlosxom. I'll be adding that as a task in the next round of adding tasks.

Additionally, this project has given me some ideas on how to better organize outstanding tasks so that it's easier for people to figure out how to help out. I'll be working on that going forward as well.

/will (willhelm at users dot sourceforge dot net)

I installed MediaWiki on SourceForge to manage and coordinate work on PyBlosxom 2.0. We're slowly building specifications which specify what PyBlosxom does in 1.4, problems with that behavior and how it should be changed for 2.0.

Discussion of the specifications should be kept in the discussion pages of the wiki and on IRC at #pyblosxom on irc.freenode.net.

PyBlosxom 1.4.1 still had issues with WSGI, Paste and running on Python 2.5. This release fixes those issues, fixes some issues with running on Windows, and has better documentation for installation.

If you're having problems getting 1.4.1 running on Windows or Python 2.5/WSGI/Paste, I highly recommend you upgrade to 1.4.2.

Download here:

http://sourceforge.net/project/showfiles.php?group_id=67445&package_id=65802&release_id=532722

If you have any problems, please toss a bug in the bug tracker.

/will (willhelm at users dot sourceforge dot net)

p.s. I did the release on 8/16/2007, but forgot to mention it on the front page. Whoops!