RE: Recommended Practice?

Would a label also make sense in this case, since I think I remember you
(Eric) saying that a label is really a pinned branch?

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Eric Sink
Sent: Monday, December 29, 2003 11:34 AM
To: [email protected]
Subject: RE: [vault-list] Recommended Practice?


I agree with Chris -- it would definitely make sense to branch in this case.
You will end up with two folders in your repository:

$/project1
$/project2

where in this case, $/project2 is the branch, and
$/project1 is the trunk.

After branching, I would pin $/project1 so nobody will accidentally change
it.

Someday you might find need to actually modify $/project1, for the purpose
of doing a maintenance release, for example.  In this case, I would branch
yet again:

$/project1.0.1

and make your maintenance fixes there.

This approach is very similar to what we use in our work on Vault.

As we've discussed several times on this list, Vault 1.x doesn't do a good
job helping you migrate changes among these branches.  Vault 2.x is better.

--
Eric Sink
Software Craftsman
http://software.ericsink.com/
 
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Chris L. Kinsman
Sent: Saturday, December 27, 2003 1:08 PM
To: dave wanta; [email protected]
Subject: RE: [vault-list] Recommended Practice?

My recommendation would be to branch the code base.  This is typically what
a branch is used for.  If you copy all the files you lose the history of
them prior to them appearing in the 2.0 tree.

 

 

Interesting to hear Eric's take.

 

chris

 

________________________________

From: [email protected]
[mailto:[email protected]] On Behalf Of dave wanta
Sent: Saturday, December 27, 2003 3:44 AM
To: [email protected]
Subject: [vault-list] Recommended Practice?

 

Hi All,

I've finished development on a 1.0 version of a project (component).

 

I want to freeze 1.0 development, and start development on 2.0.

 

What is the recommended practice for doing this with vault?  I want to keep
all of my 1.0 files "etched in stone", and only to be used when I need to do
builds, bug fixes, tests, on this 1.0 version. I want do keep this 1.0 copy
around, so that when I'm on version v.NEXT (ie v2, v3, v4, etc..), I can
always go back, and see how certain functionality worked in 1.0.

 

What is the recommended practice for achieving this with vault? 

 

Should I just create a new repository and call it "Project2.0" (or something
like that), and copy all of the files into the 2.0 project?  Do I branch?
Any whitepapers I can read on this?

 

Thanks,

Dave


_______________________________________________
vault-list mailing list
[email protected]
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list