python-ldap-dev

Re: Tagging the CVS archive

[Konstantin C. <Kon...@da...>]

Hi All,

I can't understand why I haven't received a few recent messages sent to
the mailing list. I've checked that I'm subscribed. Anyway,

>     FROM: Steffen Ries
>     DATE: 07/15/2001 06:17:50
>     SUBJECT: RE:  Tagging the CVS archive
>
>     Michael Ströder <> writes:
>
>     > 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 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
>     ...
>
Are you sure the tags are case sensitive?
The other thing: I'd personally prefer (I'm not insisting though :-) "_"
instead of "-".
In any case, if we're going to have branches dependant on the OpenLDAP
API support, they could be called just OPENLDAP_1 or similar, while
releases could be named REL_1_11 and REL_1_10.

Unfortunately, I don't have enough experience in CVS to make branches.
Could somebody do that?

Regards,
    Konstantin.

--
          * *        Konstantin Chuguev - Application Engineer
       *      *              Francis House, 112 Hills Road
     *                       Cambridge CB2 1PQ, United Kingdom
 D  A  N  T  E       WWW:    http://www.dante.net

Re: Tagging the CVS archive

[Michael <mi...@st...>]

Konstantin Chuguev wrote:
> 
> In any case, if we're going to have branches dependant on the OpenLDAP
> API support, they could be called just OPENLDAP_1 or similar, while
> releases could be named REL_1_11 and REL_1_10.

Today nobody is building with Netscape or Novell libs anymore, I
guess.

Branches for OpenLDAP API (e.g OPENLDAP_1 and OPENLDAP_2) and tags
for releases (e.g. REL_1_11). Does that make sense to you folks?

> Unfortunately, I don't have enough experience in CVS to make branches.

Me too.

> Could somebody do that?

David?

Ciao, Michael.

Re: Tagging the CVS archive

[Konstantin C. <Kon...@da...>]

Hi All,

I think there's no point to postpone introduction of the OpenLDAPv1 branch
in the CVS. I can do that, I just need an approval from one of the project
admins.
The proposed name is openldap_1_branch. It will be made on both python-ldap
and htdocs directories.
After that we could just reflect branching in htdocs/faq.shtml (or
somewhere else) and then update the latter in the current branch to reflect
LDAPv3/OpenLDAPv2 support (after submitting the corresponding patches, of
course :-)

Any objections?

A small question: there are HTML links to files in htdocs/doc/ directory
from htdocs/docs.shtml file, while there's no such directory. Why?

Regards,
    Konstantin.

--
         * *       Konstantin Chuguev           Francis House
      *      *     Application Engineer         112 Hills Road
    *              Tel: +44 1223 302992         Cambridge CB2 1PQ
D  A  N  T  E      WWW: http://www.dante.net    United Kingdom

Re: Tagging the CVS archive

[Michael <mi...@st...>]

Konstantin,

sorry for answering that late.

Konstantin Chuguev wrote:
> 
> I think there's no point to postpone introduction of the OpenLDAPv1 branch
> in the CVS.

Agreed.

> I can do that, I just need an approval from one of the project
> admins.

Hmm, not sure if I'm a project admin. Well, I'm listed there...

> The proposed name is openldap_1_branch. It will be made on both 
> python-ldap and htdocs directories.

Please use capital letters OPENLDAP_1_BRANCH but not on the htdocs/
directory. Go for it.

> A small question: there are HTML links to files in htdocs/doc/ directory
> from htdocs/docs.shtml file, while there's no such directory. Why?

The directory htdocs/ is solely dedicated to manage the web pages on
http://python-ldap.sf.net. Leave that out. It's not part of a
release tar-ball.

Ciao, Michael.

Re: Tagging the CVS archive

[Konstantin C. <Kon...@da...>]

Hi Michael and All,

Michael Ströder wrote:

> sorry for answering that late.
>

No worries, same problem here: I have been too busy last couple of months...

I have just tagged the repository with the OPENLDAP_1_BRANCH tag. Everything
seems to be OK, at least I can see and choose that tag in the Sourceforge
web-to-CVS gateway.
Anybody willing to roll out the release for OpenLDAPv1?
I'm going to add OpenLDAPv2 patches soon. The first goal is to handle
referrals, the second one is a new version of the rebind_proc callback. Note
that in the C API, OpenLDAPv1 rebind_proc is incompatible with OpenLDAPv2. I do
not see the way of providing compatibility between them, because the callback
mechanism itself has changed completely. So I think we need a change in
python-ldap API as well. Do you have any suggestions about it?

Regards,
    Konstantin.

>
> Konstantin Chuguev wrote:
> >
> > I think there's no point to postpone introduction of the OpenLDAPv1 branch
> > in the CVS.
>
> Agreed.
>
> > I can do that, I just need an approval from one of the project
> > admins.
>
> Hmm, not sure if I'm a project admin. Well, I'm listed there...
>
> > The proposed name is openldap_1_branch. It will be made on both
> > python-ldap and htdocs directories.
>
> Please use capital letters OPENLDAP_1_BRANCH but not on the htdocs/
> directory. Go for it.
>
> > A small question: there are HTML links to files in htdocs/doc/ directory
> > from htdocs/docs.shtml file, while there's no such directory. Why?
>
> The directory htdocs/ is solely dedicated to manage the web pages on
> http://python-ldap.sf.net. Leave that out. It's not part of a
> release tar-ball.
>
> Ciao, Michael.

--
         * *       Konstantin Chuguev           Francis House
      *      *     Application Engineer         112 Hills Road
    *              Tel: +44 1223 302992         Cambridge CB2 1PQ
D  A  N  T  E      WWW: http://www.dante.net    United Kingdom

Re: Tagging the CVS archive

[Steffen R. <ste...@sy...>]

Konstantin Chuguev <Kon...@da...> writes:

...
> >     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
> >     ...
> >
> Are you sure the tags are case sensitive?

Yes.

> The other thing: I'd personally prefer (I'm not insisting though :-) "_"
> instead of "-".

Works for me too :-) (I was used to "." for separating parts of tags,
but this works with ClearCase, not with CVS, so I started to use -
instead...)

> In any case, if we're going to have branches dependant on the OpenLDAP
> API support, they could be called just OPENLDAP_1 or similar, while
> releases could be named REL_1_11 and REL_1_10.

I think it is better to have some naming convention which
distinguishes branches from releases. E.g. "openldap_1_branch".
 
> Unfortunately, I don't have enough experience in CVS to make branches.
> Could somebody do that?

cvs tag -b <branchname>
vs.
cvs tag <tagname>

I don't have access to CVS...

/steffen
-- 
ste...@sy...	<> Gravity is a myth -- the Earth sucks!