Re: pyblosxom 1.2 timeline

Ok.  Given what I've heard so far, I think PyBlosxom 1.2 will have:

  - Steven's changes for wsgi, mod_python and other framework support
  - fixes to the static rendering
  - minor fixes to other things
  - better documentation

Then we'll push the other issues to the next version of PyBlosxom:

  - better international support
  - index cache support (which probably involves re-writing the file
    handling)


Anyone averse to that?  I was tossing around trying to slam-dunk the index 
cache support, but I don't think I can do it in the next few days 
(certainly not without Bill's help [no worries about taking a break, 
Bill]) and that's something that should really spend some time cooking in 
CVS before we unleash it upon the world.

If we're kosher with this, then I'll spend the next week moving the 
PyBlosxom manual to docbook and check it in.  I'm going to ditch the 
ability to comment on individual chapters--no one's used the feature and I 
don't think anyone really cares much.  We could probably slide it in 
afterwards anyhow with a fancy plugin.

It'd be nice to go through our existing contributed plugins and make sure 
everything works with the future PyBlosxom 1.2.  Additionally, we should 
go clean up the code so that all contributed plugins conform to our latest 
standards.

Also we need to get together better documentation for the latest comments 
plugin.  I saw a few emails about preview, nospam, and such--it'd be good 
to document that so that it's easier for users to figure out what's going 
on.  That should probably be a separate document from the PyBlosxom 
manual.

How's that?

/will


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click