Re: pyblosxom web-site update

> For me HEAD and DEVEL seem synonymous.  Branches should be used for 
> highly experiment or potentially sweeping changes and should be 
> integrated back into HEAD after some amount of review.  A lot of this 
> would be easier under svn.

Yes, HEAD seems to be the same as DEVEL for now. I do believe that 
people would checkpoint HEAD and pretty much complain if things didn't 
work, pyblosxom is a small project, so I don't think people will 
complain, but I believe it is a good habit to follow.

Web have branches for all older versions so people can make changes or 
bug fixes to it if they need to. Not just for bleeding edge 
experimental stuff. Long time ago, we'd survive by just tagging. I'd 
just checkout pyblosxom_0_8 and create diffs from there. Pyblosxom is 
bigger that I'd expect it to be now, and since you can't check in to 
tags, and committing to HEAD is dangerous from older versions (like 
0.8) it then becomes easier if we had branches for older versions. The 
other side of it is that if there is a security issue that affects all 
pyblosxom version, we'd have to fix that on all branches :(

Right now we have PYBLOSXOM_1_2, PYBLOSXOM_1_1 and PYBLOSXOM_1_0 
branches. According to Will, we don't need to go further than that.

Just work on DEVEL and when we release, I'll merge to HEAD. If anyone 
else who has worked on big multi versioned projects and have a better 
methodology for source code  repository, please tell us. We might like 
it and try out your idea. For now this is what works for me at work and 
is the only way I know best.



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