sprint week for pyblosxom 1.5

Hi!

Sean and I talked about sprints on IRC yesterday and decided that
instead of doing a single minor sprint, we'd do a 7-day sprint!

Thus, I hereby welcome you all to Sprint Week for PyBlosxom 1.5!

The Sprint Week will start on Thursday, March 10th and end a week later
on Thursday, March 17th.  The goal of the sprint is to finish everything
off so we can do a PyBlosxom 1.5 release.  This will make us all much
happier.

I encourage you all to participate, even if it's doing one thing on the
list.  If you need any help, send an email to the pyblosxom-devel list.
 9 times out of 10, you'll need help because I didn't document something
appropriately.

Here's a non-exhaustive list of things that I'd like us to work on over
the sprint week:


1. There are a list of issues marked with the 1.5 milestone.  Working on
these definitely gets us closer to a 1.5 release.

Working on flavour packs, updating the plugin registry, and updating the
documentation don't require and coding skills.

2. Also in the 1.5 milestone are a bunch of issues that were ported over
from SourceForge bug tracker.  You can recognize these because they all
have ID: xxxxx at the end of the issue title.  These need to be triaged.
 It's possible that some of these aren't issues anymore.

3. Going through the bug tracker for bugs that should be in the 1.5
milestone, but aren't.

4. Getting the most recent PyBlosxom from git and running the unit
tests.  If you bump into failures, write up an issue for each one.

If you're able to fix the failures, sending patches is fantastic!

5. Fixing any other issues you have with PyBlosxom or the plugins or
even writing new plugins.

6. Writing up issues for problems with the web-site, infrastructure, or
other things.

This doesn't require coding skills.


I'm at PyCon 2011 from Thursday through Wednesday during much of this
sprint.  I'll be checking email and I'll be on IRC when I can be.  I'll
also plan to spend some quality time with PyBlosxom towards the end of
the conference.

I encourage you to participate.  If there's anything that makes
participating difficult, let me know and I'll work on reducing barriers
to entry and blocks as much as I can.  I'd love to get this release out
the door, but I can't do it alone (unless we all want to wait another 6
months).

Let the sprint begin!

/will

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d