On Sun, Dec 30, 2012 at 11:40:09AM +0800, Paul Wise wrote: > I do wonder how the PTS should cope with this change though, any > thoughts? Looks like the two formats are easily mechanically distinguishable: the new one has one extra field. So a viable migration plan with no down time is: (1) patch the PTS code to act differently depending on the number of fields and deploy the change; (2) deploy the change on the lintian infrastructure and rebuild qa-list.txt. Given that not all future format changes would have the luck of being mechanically distinguishable, it might be a good idea to take this chance to add a declared format version, e.g. a first line in qa-list.txt starting with "#", declaring the format name and version. That would make it easy future migrations, if the need arises. I don't think the PTS code currently ignore #-commented lines, so that should be added too. HTH, Cheers. -- Stefano Zacchiroli . . . . . . . zack@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
Attachment:
signature.asc
Description: Digital signature