On 26-Jan-08, at 6:01 PM, claudia logan wrote:
> Thank you, I will try the script.... Any thoughts on the 2nd question?
It's very much related. If you have a directory in your repo which
contains everything pertinent to a release (typically trunk) – your
"public library" and related projects, for instance – then you tag by
copying that subtree. If you wish to release Project B only, then you
can make a tag by copying just "public library" (whatever version is
pertinent) and "Project B" to the new tag directory (to repeat what I
sketched before).
—Toby
>
>
> ----- Original Message ----
> From: Toby Thain <toby_at_smartgames.ca>
> To: claudia logan <cvlogan1_at_yahoo.com>
> Cc: users_at_subversion.tigris.org
> Sent: Saturday, January 26, 2008 5:51:09 PM
> Subject: Re: Best practices rookie question.
>
>
> On 26-Jan-08, at 7:47 AM, claudia logan wrote:
>
>> I guess I am old school. I am used to my release baseline ONLY
>> containing was was actually released. As I would need to know
>> exactly what was released for any given release.....hmmm I am
>> concerned, how would subversion track this?
>
> Off the top of my head, your release process/script could simply
> create a 'release' tag with whatever structure you wish. It need
> not correspond to a single complete copy of trunk although as other
> posters point out, it is rather conventional. If your trunk
> includes things that are entirely extraneous to your release, you
> could take a subtree, or even build up a subtree under the tag from
> disparate directories (you might want to do this in a single
> commit, perhaps using svnmucc http://svn.collab.net/repos/svn/trunk/
> contrib/client-side/svnmucc/ )
>
> IANAE but I suggest you simply do what is most comfortable and
> logical for your release process.
>
> —Toby
>
>>
>> ..and regarding my 2nd question - any thoughts?
>>
>> Question 2: Since I need "Public library-v1.0" as part of Project
>> B, what is the best way to package it as one tool? The goal being
>> that by extracting the project-tag, it will contain all that I
>> need to release. What I've done, is export the version "Public
>> library-v1.0" into my "Project B - tag". and then update my
>> tag...But it does not seem right. What is the best way....
>>
>> Please help !
>>
>> ----- Original Message ----
>> From: Blair Zajac <blair_at_orcaware.com>
>> To: claudia logan <cvlogan1_at_yahoo.com>
>> Cc: users_at_subversion.tigris.org; Paul Koning
>> <pkoning_at_equallogic.com>; marc gonzalez-carnicer
>> <carnicer.lists_at_gmail.com>
>> Sent: Saturday, January 26, 2008 1:38:15 AM
>> Subject: Re: Best practices rookie question.
>>
>> It's actually clearer if you only tag/branch trunk and never
>> delete anything.
>> Otherwise people used to Subversion will wonder where you tagged/
>> branched from
>> and cause more confusion.
>>
>> The tags/branches consume no additional server space, so there's
>> no harm.
>>
>> Blair
>>
>> --
>> Blair Zajac, Ph.D.
>> CTO, OrcaWare Technologies
>> <blair_at_orcaware.com>
>> Subversion training, consulting and support
>> http://www.orcaware.com/svn/
>>
>> claudia logan wrote:
>> > O.k but in creating the tag - I only want what is released. If
>> those
>> > directories are not really part of my baseline, why "tag" it?...
>> This
>> > will create confusion in the future..
>> >
>> > ----- Original Message ----
>> > From: Paul Koning <pkoning_at_equallogic.com>
>> > To: marc gonzalez-carnicer <carnicer.lists_at_gmail.com>; claudia
>> logan
>> > <cvlogan1_at_yahoo.com>
>> > Cc: users_at_subversion.tigris.org
>> > Sent: Friday, January 25, 2008 9:31:50 PM
>> > Subject: RE: Re: Best practices rookie question.
>> >
>> > Given that branches are "free", my practice is simply to branch
>> right
>> > near the root of the repository. Much of the branch isn't
>> needed, but
>> > it doesn't cost anything. The part that isn't needed won't
>> change, so
>> > it takes no extra space to speak of.
>> >
>> > Don't bother deleting what you don't need, you're (1) wasting
>> time, and
>> > (2) wasting space -- because it takes more space to record the
>> deletion
>> > than to leave things alone.
>> >
>> > This is one place where you really need to unlearn your CVS
>> lessons --
>> > CVS branching is very very bad while Subversion does this right
>> and very
>> > efficiently.
>> >
>> > paul
>> >
>> > > -----Original Message-----
>> > > From: marc gonzalez-carnicer [mailto:carnicer.lists_at_gmail.com
>> > <mailto:carnicer.lists_at_gmail.com>]
>> > > Sent: Friday, January 25, 2008 9:24 PM
>> > > To: claudia logan
>> > > Cc: users_at_subversion.tigris.org
>> <mailto:users_at_subversion.tigris.org>
>> > > Subject: Re: Best practices rookie question.
>> > >
>> > >
>> > > hi,
>> > >
>> > > 2008/1/26, claudia logan <cvlogan1_at_yahoo.com
>> > <mailto:cvlogan1_at_yahoo.com>>:
>> > > > Question 1: Using TortoiseSVN, How do I create a branch
>> > > where only 3 of the
>> > > > 5 directories are branched. what are the best practices.
>> > > What I have done
>> > > > is branched the complete trunk then remove what I dont
>> > > need. But that seems
>> > > > counterproductive. I updated the repository twice when
>> > > there was no need.
>> > >
>> > > i would not remove after branching. if you merge back to
>> trunk, the
>> > > removed items will be removed.
>> > >
>> > > >
>> > > > Question 1b: related to above, but instead of folders,
>> > > individual files. I
>> > > > may need 5 documents out of 10. All located in the same
>> > > area. How do I tag
>> > > > only what I need, leaving the rest?
>> > >
>> > > it seems you haven't remarked yet that copying (branching) is
>> > > 'cheap', i.e., it
>> > > does not take up disk space. otherwise, i don't see why you
>> > > would want to
>> > > tag some subset of the files.
>> > >
>> > > if you really need to release a subset of documents, what i'd
>> do is :
>> > >
>> > > * create a release/export folder on the repo
>> > > * svn copy there the needed files
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
>> > <mailto:users-unsubscribe_at_subversion.tigris.org>
>> > > For additional commands, e-mail: users-
>> help_at_subversion.tigris.org
>> > <mailto:users-help_at_subversion.tigris.org>
>> > >
>> > >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
>> > <mailto:users-unsubscribe_at_subversion.tigris.org>
>> > For additional commands, e-mail: users-help_at_subversion.tigris.org
>> > <mailto:users-help_at_subversion.tigris.org>
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> ---
>> > Never miss a thing. Make Yahoo your homepage.
>> > <http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs>
>>
>>
>>
>> Looking for last minute shopping deals? Find them fast with Yahoo!
>> Search.
>
>
>
> Looking for last minute shopping deals? Find them fast with Yahoo!
> Search.
Received on 2008-01-27 02:18:10 CET