From: Michael <mi...@st...> - 2001-07-13 10:59:37
|
Konstantin Chuguev wrote: > = > I've just committed the memory leak fix for OpenLDAPv1 only, Great! > to avoid dealing with OpenLDAPv2 before we get a new release. > After that, I'll start committing OpenLDAPv2 patches with memory leak = > fixes included. Yepp. > > See also my inquiry about CVS tagging on the list. > = > Haven't received it yet. I already received it through the list. Attached it again below. > The new OpenLDAPv1-only version: should it be 1.10beta1 or 1.11? People were used to 1.10alpha3 as a release and refer to it as version 1.10. To avoid a mess the next release should be 1.11 as already set in CVS. Ciao, Michael. -------- Original Message -------- Subject: Tagging the CVS archive Date: Fri, 13 Jul 2001 02:11:01 +0200 From: Michael Str=F6der <mi...@st...> Reply-To: mi...@st... Organization: stroeder.com To: python-ldap-dev <pyt...@li...> 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... :-/ Ciao, Michael. _______________________________________________ Python-LDAP-dev mailing list Pyt...@li... http://lists.sourceforge.net/lists/listinfo/python-ldap-dev |