On Tue, 2004-12-28 at 23:56 +1100, msevior@physics.unimelb.edu.au wrote:
> Tomas if you have bugs that require code for 2.4 to fix then these should
> be retargeted as 2.4 bugs.
> Once we're happy with the state of the fixes in HEAD after branching the
> code can be either backported or we tell users to wait until 2.4
>
> I guess the main point is to round up and squash all the fixable 2.2.x bugs.
>
As an aside, for isolated (large or small) 2.4-new code, there's
nothing wrong with attaching pathes in bugzilla to help keep track of
them and make sure they aren't obfuscated by other wd changes. This has
been done successfully in the past - assigned dev fixes locally, makes
diff, attaches to bug, and does a clean update. Later on line is
branched, dev downloads and applies patch, tests one last time, commits.
I do think you've got the right idea here martin.
-MG
Received on Wed Dec 29 18:45:36 2004
This archive was generated by hypermail 2.1.8 : Wed Dec 29 2004 - 18:45:36 CET