Beefy Boxes and Bandwidth Generously Provided by pair Networks Joe
No such thing as a small change
 
PerlMonks  

Re^2: How to best control non-working code with source control?

by radiantmatrix (Parson)
on Apr 15, 2008 at 18:02 UTC ( #680606=note: print w/ replies, xml ) Need Help??


in reply to Re: How to best control non-working code with source control?
in thread How to best control non-working code with source control?

I take your points about using branches, however:

If you spin-off a part of the development effort into a version-control system that is entirely disjoint from the one that the enterprise as a whole is using

That's not what I've done. Essentially, I have a "scratch" area where I can try things out, because the corp. policy says "no check-ins of non-working code". When I do fix a problem or add a feature, that immediately gets synced and checked into the corp. CVS -- so it isn't disjoint.

I essentially did with CVS what git seems designed to do (and better) -- created a local version history for code that isn't ready to share with others yet.

Based on your comment and others', it seems like the only real option I have is to try to get policy changed to allow me to create "unofficial" branches that contain non-working code, or to continue to do the bastardized process I have today.

<radiant.matrix>
Ramblings and references
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet


Comment on Re^2: How to best control non-working code with source control?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://680606]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (14)
As of 2014-04-18 20:17 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (471 votes), past polls