Alan Conway wrote:
OK, you've convinced me this might work out better. I suggest a single
after_M3 branch for anyone doing post-M3 work so we don't have multiple
independent feature branches to integrate after the freeze. After the
freeze we can merge after_M3 back to trunk and delete the branch.
Aidan can you create an after_M3 branch from the point we declare the
trunk frozen?
I think the responsibility for creating a feature branch and merging it
back should lie with the feature developer(s) themselves.
I don't think a general after_M3 branch is conducive to encouraging the
community to focus on getting a good release together.
