pyblosxom 1.2 timeline

Ted sent an email regarding the PyBlosxom 1.2 timeline.  I started to 
reply to that email but then figured it's better off as its own thread.

The only timeline we have is a "if it's done, then we'll release it" one.
I think to be done, we'd need the following completed and tested:

   1. pyblosxom wsgi, mod_python, and other interfaces
   2. redo the file handling so we can allow for index caching
   3. pyblosxom i18n
   4. static rendering fixes
   5. refactoring of various pieces

In regards to item 1, I think Steven is still going strong.  It's either
finished or pretty close to done.  If anyone can try PyBlosxom out in
these other frameworks, that'd help a lot.

In regards to item 2, Bill did some work, but I'm not really psyched about
it and want to investigate expanding the task and fixing a few other
issues as well.

In regards to item 3, I have no idea where we are.

In regards to item 4, there's a bug (or two bugs) in the bug tracker that
talk about static rendering problems.  Someone (I think it was Steven)
mentioned static rendering issues a few months ago.  I don't really know
where we are with this either.

In regards to item 5, Bill mentioned some things that should get
refactored because they're ugly.  While that's important to do at some
point, I'm not thinking it's really important for 1.2 and don't want to
break functionality.

And documentation needs work.  I have some stuff half-written that needs
to be finished and go into the "manual".  I also need to fix the manual so
that it's versioned alongside PyBlosxom (i.e. we have a 1.1 manual that's
separate from the 1.2 manual...).

If anyone's playing in the code and wants to spruce up the doc-strings in
the vicinity of where they're playing, that's always a big help.


I think everyone who's working on stuff for 1.2 should send a quick status
report.  I'll collate the reports into a "this is where we are" thing and
post it on the web-site.  From that we can figure out how ambitious we
want to be for 1.2 and go accordingly.

Can everyone try to send some kind of "this is what I'm working on and 
this is where I'm at" report before Monday?

/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