Hi Dennis! > I respect your opinions Mario but I'm afraid we don't see this the same way. Ok. Its just a discussion :-)
> I tend to lean towards *more* time between branch/tag and release. During > that time, no new features - only bug fixes that are moved to trunk after > release (at the latest). > +1 to no new features, but I dont understand why we should do this on the branch. This requires that we all checkout the correct branches and work on them during the whole test phase. Just to merge them with the trunk then - which is error prone. Why cant we just sensibilize the developers to not add new features to the trunk during the release process (which should not take more than a week) and then create a e.g. 1.1.2-RC1 and so on until the vote for the release goes through. No merge back required. Less work after the release, development can continue immediately. Ciao, Mario
