pyblosxom 1.1 released

I'm not wildly psyched about this release, but it's good to get it out the 
door.

Moving on to 1.2....  I'm thinking we should wait a month or so until this 
release has cooked in case 1.2 needs to be a problem fixing release. 
After that, I'm thinking we should work on the following issues:

1. storage api - we need to fix the way we pull entries from the file
    system to allow for index caching.

2. internationalizing - we need to make sure that all of PyBlosxom
    (including plugins) works with UTF-8 and other character encodings.

3. contributed plugins - I'm thinking this is its own project with its
    own release schedule.  Anyone want to volunteer to become the
    maintainer of the contributed plugins project?

There are performance issues and such as well, 
but I think we'll enable people to fix those with plugins more easily 
after we fix the storage api issue.

On another note, I don't have wild amounts of free time.  Ultimately, I'd 
like to continue maintaining the pyblosxom core stuff and work on 
documentation and that's about it.  So someone (or multiple someones) need 
to pick up the slack on the contributed plugins.

Sorry for the incredible delay with the 1.1 release.  And additionally I'm 
sorry I didn't get to sit down and go through it with a fine-toothed comb 
like I had wanted to.  I use 1.1 exclusively, but I don't really know what 
the state of it is outside of my usage.

I think that covers it.  Any thoughts?

/will

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt