...
Doesn't sound like branch processes are broken
Michael proposes the following (picking on Seth and David): get them to write up the process and get it posted. Then we will start following it. E.g. the Jira type is bug etc.
may be value in broadening the branch mgmt process to get second opinions on whether it passes. Doing it in some areas such as involving Jim Eng in Resources issues. Document this as part of the process. Recommendation of a project leader is a good stamp of approval.
2.5.1 and # of components that were touched and the number of tests needed.
Can these fixes be clustered in narrower focus to make testing easier.
Could be tough to track the modules and the clustering
Megan says can work around needed fixes by version release vs maintenance branch
If I f 2.5.2 and 2.5.3 come out only a month apart this makes tracking easier
...