lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: Migration to SVN?
Date Mon, 20 Dec 2004 16:11:39 GMT
I don't know how exactly SVN works, but one of the things we have
talked about in the past is that we currntly do not tag, branch, and
release sandbox components, and we all agree that we should.
Furthermore, because of API changes, keeping core and sandbox in sync
is important.  Perhaps we can make our lives simpler by tagging,
branching, and releasing sandbox WHENEVER we tag, branch, or release
the core, and we could do it in the way that keep tag, branch, and
release names in sync.
Something like:
  lucene_core_1.4.3 -- lucene_sandbox_1.4.3
  lucene_core_2.0.0   -- lucene_sandox_2.0.0

I'm not sure which directory structure would be best for this, but this
is an issue we've repeatedly talked in the past, so we should strngly
consider whichever structure permits this with the least effort.

SVN users: which of the structures proposed so far satisfy this?

Thanks,
Otis

--- Garrett Rooney <rooneg@electricjellyfish.net> wrote:

> Giulio Cesare Solaroli wrote:
> > I am not a commiter (just an happy user!), but I would suggest the
> > following layout:
> > 
> > asf-repo/
> >   jakarta/
> >     lucene/
> >       trunk/
> >          core/
> >          sandbox/
> >       branches/
> >       tags/
> > 
> > This layout will allow tags and branches of both core and sandbox
> to
> > be kept in sync without any effort.
> > 
> > Does this make any sense?
> 
> Six of one, half dozen of the other.  Honestly, I prefer to split the
> 
> projects out and give them their own trunk/branches/tags directories,
> 
> just because it seems cleaner to me and additionally because it's the
> 
> way other projects I've known at the ASF run things.  I like to be
> able 
> to look in the branches and tags directory and know what the 
> tags/branches correspond to immediately, as opposed to this kind of 
> layout where a branch/tag could be just the core, just the sandbox, 
> both, etc.  You wouldn't want to always branch/tag both, but
> sometimes 
> you might, the ambiguity bothers me.
> 
> -garrett
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


Mime
View raw message