So, how to people manage living code under CVS? We have sandbox,dev,pre-prod,prod and disaster recovery systems all running Perl. In the past we would tag files for a release and then cvs upd -r tagname to bring the various systems up to date. This worked rather well, but the major downfall being when we need to make a fix we move the tag on the existing file (or occasionally branch if necessary). When moving a tag, however, you lose track of what was on prod before the tag is moved.
We're trying keeping prod on its own full branch but that causes issues as well. For one, merging onto the prod branch almost always causes conflicts (that we ignore), for two it is not exactly obvious how to handle reverting code if a delivery goes horribly wrong. We could use cvs's date updating but files are often on the ppe system days before they go out, and going by date won't give us the state of the prod server as it was on a certain day necessarily.
Other people must be working in situations like this, how do you handle keeping track of your production code in a living web application?
- Some of my
best work - (1 2 3)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||