pyblosxom over the next week

will <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <[email protected]>
A couple of people have told me they have some free time over the next 
week and want to do some PyBlosxom stuff.

I've been documenting some tasks that need to be done on the wiki here:

http://pyblosxom.sourceforge.net/wiki/index.php/Category:Tasks

I tossed a few more tasks in there and adjusted the ones that have been 
completed through the GHOP.

I've been dragging my feet working on adding testing for 
blosxom_process_pathinfo--it's hard because there are a bunch of 
template variables that aren't very well specified and have funky 
behavior.  root_datadir comes to mind.

Also, PyBlosxom needs to be tested on Windows, Mac OSX and with Python 
2.3 and 2.4.  If anyone can run PyBlosxom tests through any of those 
environments, that'd be super duper.  Any bugs discovered should get 
tossed in the bug tracker:

http://sourceforge.net/tracker/?atid=517918&group_id=67445&func=browse

Going through all the existing plugins and making sure they work with 
PyBlosxom is also a good thing.

I think that covers it.  I'm gone after today.  Please coordinate with 
each other through this mailing list and/or on IRC #pyblosxom on 
irc.freenode.net.

Also, I wanted to release 1.4.3, but didn't get there.  If people could 
test that and make sure the changes made are good, then I'll release it 
when I get back.

I'm really excited about the future of PyBlosxom.  Good luck everyone! 
See you next year!

/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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.