Advice on process for web development
From: Giulio Troccoli <Giulio.Troccoli_at_uk.linedata.com>
Date: Fri, 29 Oct 2010 13:20:00 +0100
I'm working with our Web Team to re-engineer their development process. All the code is already under Subversion, but everything is in one big directory. They're not using any branch or tags for that matter. And of course, testing is not as rigorous and controlled as it should be. Anyway, I have suggested the usual trunk/branches/tags layout.
Developers will normally work on branches, but can occasionally work directly on trunk for easy and quick fixes. The tester will create a QA branch as a copy of trunk at a specific revision. When they are happy that a QA is ready for releasing, a tag is created from the QA (or maybe from trunk again at the same revision).
I think they will go for such a solution, even though it means that they cannot pick-and-choose what to test. If they want to test a bug fixed in revision 1000, they will also test all bugs fixed in previous revision.
The problem is that they may want to fast track an urgent bug fix. It shouldn't happen often, but it may happen so I need to come up with a solution for that case too.
What I'm thinking is something like the following. Let's supposed that 1.1 is the latest release, i.e. it's what's in production.
Now my questions.
Thank you in advance.
This is an archived mail posted to the Subversion Users mailing list.