Comment 49 for bug 1823200
Revision history for this message
| Brian Rosmaita (brian-rosmaita) wrote | #49 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
@pcheli: I'm sorry for not mentioning this sooner, but I think you need to increment the version number and version history on the driver in each branch so that it will be easy for operators to tell if they are using a fixed driver or not. Just be sure to pick a number that won't conflict with a more recent branch (e.g., stein is at 2.0.4 and a 2.0.5 was already included in train.
Maybe Sean or someone can suggest the best way to handle this. I'm not sure if you can make the new stein driver 2.1.4 or whether you should make it 2.0.5.1