QuicksearchArchivesCalendar
|
Tuesday, April 28. 2009Real dependencies, not convenient dependenciesTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
This idea sounds so logical it screams to me: "why isn't this the current policy?!" I then think of the work that will be required of the Debian maintainers and Ubuntu MOTU to fix these issues. Hopefully it would be as easy as going through the changelog of the package src and rebuilding against the older set of minimal dependencies and seeing if it still works.
On your related gripe: In the language of Launchpad, the current work flow is indeed the correct work flow. However, if you do see a bug fix which should be backported to an LTS, then there is always the option of opening a task against the LTS. That new task will then be reviewed to see if it should be backported or not. It is a little wonky sounding at first, but it is pretty much the only way to keep the bug tracker sane.
Hmm...I understand that may be the language, but when you report a bug, you report against a certain version (whether that be the version of the package or the version of the Ubuntu release). I guess then, it should be policy to open a backport request upon closing the bug if the bug was originally opened against a version that is still in its supported phase.
|
self.about()My name is Joshua Kugler, and I'm a programmer/developer and a system admin. On this here blog, I pontificate about all things related to code, work, projects, and sometimes just life. Look around, snag my RSS feed, and drop me a line, if you wish. All opinions are mine, and not necessarily those of my employer.
self.links()CategoriesCopyright |
|||||||||||||||||||||||||||||||||||||||||||||||||