Tagging the CVS archive

[Steffen Ries]

Michael Ströder <michael at stroeder.com> writes:

> HI!
> 
> Could we find some meaningful set of tags to mark the python-ldap
> CVS archive? Maybe we can borrow some ideas from
> http://www.openldap.org/software/repo.html ?
> 
> I'd like to check in the new OpenLDAP 2-related patches and memory
> leak fixes since I spent some time sending patch mails around. But
> before that I'd like to mark the current CVS version with
> PYTHONLDAP_REL_ENG_1_2 or something alike. Not being a CVS expert
> though... :-/

I think you should create a branch tag for OpenLDAP 1 related
stuff. That way both fixes for the "old" API and new stuff can go in
in parallel.

I would suggest a scheme where upper case tags are applied to
releases, and lower case tags are branches.

e.g.:
REL-1-10ALPHA3
REL-1-11
...
openldap-1-api
...

The head revision ("main trunk") holds the latest and greatest
version, leading towards the next major release. The side branch is
for fixing bugs in the current release (memory leaks...). The
openldap-1-api branch should lead to a 1.10final release.

/steffen
-- 
steffen.ries at sympatico.ca	<> Gravity is a myth -- the Earth sucks!