Dennis Byrne wrote:
Well, I think the reduction in the use of "externals" in the svn
repository may help a little; it's easier to create branches now.
But the major work is still a matter of ensuring that patches for bugs
are applied to both a branch and the trunk, or of someone trawling
through all patches applied to trunk and "back-porting" them to a bugfix
branch. That's not really related to the build system at all.
Are there policies for committers on this? There is a subtle difference between
committing the fix and closing the issue, vs. creating a patch, attaching it to the
issue, committing the change and then closing the issue. The second makes it easier for
"back-porting", which is something both MyFaces or an external organization may
want to do.
Well, when someone commits a patch to svn which is related to a JIRA
issue, they *should* include the jira bug number in the commit message,
like:
Fixed MYFACES-789 - twiddled the widget
JIRA monitors the svn commits so that going to the JIRA issue and
selecting the "subversion commits" tab then shows which commits were
associated with this issue. And from there it's trivial to get the patch.
Regards,
Simon
