warning about tracking trunk, template spec, #pyblosxom, et al

If anyone is keeping up with changes in the trunk and using that for
their blog or some other production thing...  I'd encourage you not to
do that for a while.

I'm breaking stuff left and right because we have some seriously assy
stuff in there that needs to be refactored but the code base is pretty
finicky.

I'll try to keep things stable, but ...  some of the things I'm
reworking are having wider repercussions than I thought they did.

Also, I'm working up a specification for templates.  I'm about half
done--it covers a lot of ground.  It's taking a lot longer than I
expected.

The specification will be like the entrycaching one and it'll specify
what we've got and what changes need to be made.  When I'm done, I'll
send it to the list (actually, I'll probably send a url to the list)
and we can talk about it.

I'm hopping on #pyblosxom more often.  I hop onto #miro and
#miro-hackers for work, so hopping on #pyblosxom is just another tab.
If anyone wants to talk about PyBlosxom design things for 2.0, hop on
and we can chat.

MediaWiki has some interesting things you have to do to get it
running, too.  Would using an external wiki like PBWiki be good
enough?  Mostly I want it to allow users to centralize PyBlosxom
"recipes" that cover other installations, environments, and usages.

/will

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/