Hi, Right now the policy for bzr-gtk seems to be that bug reports get marked "fix committed" as soon as their fix enters trunk, and that they get marked "fix released" when after their fix has ended up in a bzr-gtk release.
Most other bzr projects (including bzr core) use a different policy and mark "fix committed" when a fix is available *somewhere* and "fix released" when the fix enters trunk. Would anybody object to using the same policy for bzr-gtk ? This should also make release management a bit easier as there wouldn't be a need to update all the bugs that were fixed in a release. Cheers, Jelmer -- Jelmer Vernooij <[email protected]> - http://samba.org/~jelmer/ Jabber: [email protected]
signature.asc
Description: This is a digitally signed message part
-- bzr-gtk mailing list [email protected] Modify settings or unsubscribe at: https://lists.canonical.com/mailman/listinfo/bzr-gtk
