-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
For a while now, we've been informally following a policy of cloning bugs into other milestones if they need to be fixed in multiple places. I'd like to formalize this as part of the process. It makes tracking much easier.
Since we're now doing this, the custom field "FixedIn" no longer has any value whatsoever (originally it was meant to denote the lowest released version that the fix could be seen in, unrelated to the milestone during which it was being fixed. It was a relic of when our milestones were time-based rather than release-based).
Unless anyone has any strong reservations about it, I'm going to eliminate this unnecessary knob from our Trac instance.
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
On Mon, 15 Nov 2010 16:09:38 -0500 Stephen Gallagher sgallagh@redhat.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
For a while now, we've been informally following a policy of cloning bugs into other milestones if they need to be fixed in multiple places. I'd like to formalize this as part of the process. It makes tracking much easier.
Since we're now doing this, the custom field "FixedIn" no longer has any value whatsoever (originally it was meant to denote the lowest released version that the fix could be seen in, unrelated to the milestone during which it was being fixed. It was a relic of when our milestones were time-based rather than release-based).
Unless anyone has any strong reservations about it, I'm going to eliminate this unnecessary knob from our Trac instance.
Kill it.
Simo.
sssd-devel@lists.fedorahosted.org