Working in DEVEL branch

Hi there, I've set up a DEVEL branch for us to work with. For now I'm 
not sure if we let HEAD be where it is, or we should revert HEAD to the 
pyblosxom_1_2.

For now, everyone can update their branch to DEVEL with the following 
simple command in the pyblosxom tree:

cvs -q update -r DEVEL

Which if you are quite updated with the CVS, you'd see nothing exiting, 
really.

You can check by looking at a status of one file, for example, the 
README file:

Vertigo:~/Sites/pyblosxom wari$ ls
CVS             MANIFEST.in     contrib         setup.cfg
INSTALL         Pyblosxom       docs            setup.py
LICENSE         README          pyunittest.py   web
Vertigo:~/Sites/pyblosxom wari$ cvs status README
[email protected]'s password:
===================================================================
File: README            Status: Up-to-date

    Working revision:    1.10
    Repository revision: 1.10    /cvsroot/pyblosxom/pyblosxom/README,v
    Sticky Tag:          DEVEL (branch: 1.10.6)
    Sticky Date:         (none)
    Sticky Options:      (none)

Or you can check the CVS/Tag file:

Vertigo:~/Sites/pyblosxom wari$ cat CVS/Tag
TDEVEL

If you have code changes in your code base, it is advised that you copy 
out those files you changed, delete them in your tree, cvs update -r 
DEVEL, and copy back those files, and update/commit. Else you might 
lose your changes, and it's not a pleasant experience.

Pyblosxom 1.1 and 1.0 is not tagged, it would be nice to know their 
release dates so that I can create branches from there.

BTW, the release_1_2 tag is there, and I'm thinking of renaming it to 
pyblosxom_1_2, etc.. any objections?



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