| |||||||||||||
Getting multiarch dpkg into DebianGetting multiarch dpkg into DebianPosted Mar 8, 2012 2:05 UTC (Thu) by rgmoore (✭ supporter ✭, #75)In reply to: Getting multiarch dpkg into Debian by rahvin Parent article: Getting multiarch dpkg into Debian
The package maintainer just wanted time to review the code to ensure it met the standards for a package that basically controls the stability of the entire distribution. The underlying problem is that the standard procedure doesn't give any kind of deadline for the package maintainer to respond. That's reasonable because there really isn't a one-size-fits-all response interval, but it means there's a danger that something will be put on the back burner and never taken off because the maintainer always sees something else as a higher priority. That seems to have been what happened in this case, and it wasn't until the technical committee gave him a firm deadline that he bumped the priority enough to do the review. The big question is whether there needs to be some general procedure for dealing with this kind of problem, or whether ad hoc solutions will work. This is a rare case where the package is on the critical release path for the whole project, so the technical committee really had to step in. But what happens when it's on a less important project that isn't going to hold up the whole release? Can a maintainer put off changes indefinitely because he wants to review everything and doesn't have time to do it? Does there need to be some kind of general process to generate a definitive answer for changes that have been delayed?
(Log in to post comments)
|
|||||||||||||