[OGo-Developer] Patches In Bugzilla
Helge Hess
developer@opengroupware.org
Tue, 27 Feb 2007 11:07:35 +0100
On Jan 18, 2007, at 15:18, Adam Tauno Williams wrote:
>> Adam, you
>> would need to check the patches one-by-one, test them and possibly
>> affected areas. And then approve/commit the patches (adding proper
>> revision numbers of patches in Svn). I would then do another quick
>> review prior doing a release.
>> Adam, would you volunteer for that?
>
> Yes; although ultimately I might not be any faster than you. :)
Two is always faster than one ;-)
> As for "Adding proper revision numbers of patches in Svn". Is there a
> guide for this?
If you do an 'svn commit' Subversion will give you a revision number
(say r23456). Just add that to the bugfix in Bugzilla ;-)
> As in some kind of [at least rough] procedure as to the
> canonical steps?
After you applied a patch to the trunk checkout, the usual procedure is:
1) bump the subminor version in the Version file of all affected
directories
2) add a description of the change to the ChangeLog file of the
associated
directories, including the subminor you just bumped (should be
obvious from
looking at the ChangeLog files).
3) commit ;-) Maybe including the bug-id and a short text in the
commit message
for reference.
Well, thats about it!
I'll try to find the time to create the account for you this week. Do
you already have a login at developer.opengroupware.org?
Greets,
Helge
--
Helge Hess
http://www.helgehess.eu/