RE: [DUG]: Version Control

[Wes Edwards]

There are ways you can minimise these problems but no silver bullet.   1. Only fix critical bugs in production and leave the rest until the next release from the Development Branch if at all possible.  This obviously depends on the bug severity and priority and the time to the next release.   2. Document the bugs you do fix very well (including the way it should be fixed) and include the production post-fix tests for these bugs into your dev testing programme.  If possible have the same person do both fixes or get the programmers to review each other's work.   3.  If the dev branch is only working on a limited range of files treat the remainder as in production.  If your version control system supports it you may want to configure it to only branch on change.  You'll need to track very carefully to ensure you don't miss any changes and you'll need to combine the two branches for thorough testing.   As always a well planned test programme, adeqaute documentation and good processes are the best ways to minimise the number of bugs that escape.   Wes Edwards NZCE,  BE,  M.IPENZ steadfast technology Phone: +64 9 820-9273 Fax:    +64 9 820-9274 Mobile: +64 21 417-307 www.SteadfastTechnology.com [EMAIL PROTECTED] P O Box 15-823, New Lynn, Auckland 1232, New Zealand Outgoing e-mail scanned by Norton Antivirus   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Mckenzie Sent: Monday, 4 November 2002 8:54 a.m. To: Multiple recipients of list delphi Subject: [DUG]: Version Control This is possibly a bit off-topic !   Having just done major release we are re-looking at our version control...   Is there a better way of maintaining development and production source code ? What we are doing is Branching and putting any "Production" bug-fixes into both branches and "Development" stuff into the Development Branch only. There is scope for errors (leaving out a bug-fix or putting in two different bug-fixes, etc)   Any ideas, thoughts, what we do's, what we should do's much appreciated...    Regards Paul McKenzie Analyst Programmer SMSS ltd.