If the policy is to wait for the release to be stable to update hplip, it means 
that hplip will always be one release off and won't work on the latest release 
until the changes are SRUed.
Besides SRUing large set of changes is huge and much more work than releasing a 
new version to the development release. Which changes also have to be approved 
by the SRU team.
Finally, hplip is on Ubuntu and several flavors's ISO which won't be recreated 
after the release and will include a broken version of hplip. 

IMHO it would make sense to release hplip on the latest development
release even if it's late in the cycle.

** Tags added: rls-cc-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789184

Title:
  toolbox.py crashed with AttributeError in initUI(): 'DevMgr5' object
  has no attribute 'DiagnoseQueueAction'

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1789184/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to