Re: CVS: versioning and branching

On 05-Apr-05, at AM 08:28, will guaraldi wrote:

> cvs commit: sticky tag `release-1_2' for file `fileentry.py' is not a 
> branch
> cvs [commit aborted]: correct above errors first!
>
> So what's going on?

Hehe, because it's not a branch. If we have a branch, say called 
PYBLOSXOM_1_2, one can:

cvs -q update -r PYBLOSXOM_1_2

# Edits file

cvs update && cvs commit


> Can someone spend some time finishing what we started in terms of 
> writing up the process for how we're using CVS now?

I'll try to fix up the CVS as soon as I can. I don't have time for 
documenting it yet though. Probably just simple documentation, not more 
than that, yet.

> Until then (or until I figure out how to do what I need to get done), 
> I can't do anything in regards to PyBlosxom 1.1 and 1.2 both of which 
> have minor cosmetic issues still. Not to mention the contributed 
> plugins pack which has a _lot_ of issues still for both the pack for 
> 1.1 and the pack for 1.2.

Wait for it Will.. If I have my way, I'd get branches for pyblosxom by 
tonight (which is your morning).



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