Rupert Smith wrote:
I just used 'production' system as an analogy, to get Rajith to try and think about this. Its not the first time he has suggested deleting the release branch. I'm not suggesting that we create branches for our internal production needs. We will be creating branches for every Apache release though, and it is certainly a good idea to keep them.
I think what is critical is for the repository to be tagged for each release. You can then always get the exact source used. Leaving the release branch open may well be a good idea (I'm not convinced it is sufficient or required, but thats a separate question). I do think it would be valuable to have a clear 'policy' for each open branch dictating what sort of updates are appropriate, what sort of process you need to go through (if any) for committing etc.
