--- Vincent Massol <[EMAIL PROTECTED]> wrote:
>
> ----- Original Message -----
> From: "Morgan Delagrange" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; "Vincent
> Massol"
> <[EMAIL PROTECTED]>
> Sent: Tuesday, April 24, 2001 3:58 PM
> Subject: Re: [DIGEST] April 22, 2001
>
>
> [snip]
> > > > One technical note that affects both Commons
> and
> > > Taglibs is the fact that
> > > > CVS branches are global to an entire
> repository.
> > > Therefore, if one taglib
> > > > (or Commons package) creates a branch "rel2",
> then
> > > nobody else can use
> > > > that name. We might want to think a little
> more
> > > about the long term
> > > > impacts of this little detail.
> > > >
> >
> > Hold on, can somebody point out a reason why the
> above
> > approach is a problem? I understand that branches
> are
> > global, but is it a big problem if two projects
> are
> > technically on the same branch? As long as you
> > perform your checkout at the correct location, I'm
> not
> > sure it makes a big difference. Or does it? What
> > problems would we be preventing by using unique
> branch
> > names?
> >
>
> Even if unique branch names is not a problem I would
> still prefer to prepend
> the branch by the component name (unless it is a
> commons release, involving
> all components).
I would tend toward simpler tags, unless there's a
compelling reason not to.
> > > Why don't we adopt the convention : <component
> > > name>_REL_<release version> ?
> > >
> > > For example, for version 1.1 of cactus that
> would be
> > > : CACTUS_REL_11
> > >
> > > So that there will be no name conflict with
> other
> > > components.
> > >
> > > > Craig
> > > >
> > > Vincent
> > >
> >
> >
> > =====
> > Morgan Delagrange
> > Britannica.com
> >
> Vincent
>
=====
Morgan Delagrange
Britannica.com
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
