Comment 23 for bug 163694
Revision history for this message
| Matthew Paul Thomas (mpt) wrote Re: Fix Committed/Released distinction is inconsistent and unproductive | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I agree that the version field is the hairiest part of the plan. It would be useful to be able to say, for example, that a security bug in Ubuntu is fixed in Ubuntu 8.04 LTS, 9.04, 9.10, and Lucid alpha 2 and later, or that a FooBarHum project bug is fixed in versions 2.2.1, 3.0.5, and trunk r775 and later. But any database schema smart enough to recognize those various version types would be quite a challenge, and I don't think solving that problem should be a prerequisite. Hypothetically, if you introduced version tracking later on, the free-form version info that had been entered for bugs fixed before version tracking was introduced would be no more problematic than the complete lack of version info for the older bugs fixed before the Fixed statuses were merged.