On 8/17/07, David Jencks <[EMAIL PROTECTED]> wrote: > I've noticed that sometimes when people merge bug fixes/changes from > one branch to another they don't include the jira number from the > original commit. This makes it exceedingly hard to figure out which > branches something has been fixed in from the jira issue or the > commit logs. > > In the future can everyone please be very careful to include jira > numbers on all branch-to-branch merges when the original commit was > associated with a jira entry. I usually provide a bit of backup by > commenting on the jira entry with the merge revision number as well.
I'm going to add it to our documentation so it won't disappear and wonder where it should end up. "Project Guidelines" [1] seems to be a goot fit, but I'm not so sure as bylaws != guidelines (?). "Apache Geronimo Development Process" [2] is good, too. Unless there're better places I'll make the choice. [1] http://cwiki.apache.org/confluence/display/GMOxDEV/Project+Guidelines [2] http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Development+Process Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
