Re: 1.2 status

On 03/18/05 01:01, will guaraldi wrote:
> I'm working on documentation, but other than that, I think we're ready for 
> a 1.2 release.
> 
> Any thoughts on that?  Is there anything else that we need to fix or do 
> for this release?  Any outstanding issues that I'm forgetting?
> 
> /will
> 

I changed a few things in README, hope that's ok (see pyblosxom-checkins).

Regarding the 1.2 release I'ld feel better if more people would have
tested the new stuff. Namely running on mod_python/twisted.
Also, has someone tested the new version on Windows yet?

Has someone looked at Bug 1081492 ("Static rendering doesn't work on
Windows")? I don't really understand what's happening there. Maybe the
dev who coded that could have a look at it. Why should/how could
PATH_INFO be os specific?

My understanding of Bug 1081604 ("Static rendering doesn't copy
non-rendered files") is:
Not a bug. Pyblosxom doesn't know anything about static resources
(images/css/whatever) and therefor can't offer a generic way to handle them.
Is this correct?

Bug 1145908 ("Using own renderer fails"): IMHO should be closed for now
and has to be reopened if it's not fixed by the changes we made.
(Personally I believe it's a bug in the users renderer. I have written
multiple custom renderers and they all worked without problems)

cheers
Steven


-------------------------------------------------------
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