*** This bug is a duplicate of bug 462961 ***
https://bugs.launchpad.net/bugs/462961
The other bug report was filed by the desktop team technical lead. I'm
afraid it's unavoidable that bug reports from the developers are going
to get attention much more quickly, since they can escalate such bugs
directly without the need of a bug triager to process the bug first.
Since becoming an Ubuntu developer is probably not the sort of solution
you had in mind, here are some other ways to get more attention on your
bugs:
- Participate in ISO testing before the milestones -
https://wiki.ubuntu.com/Testing/ISO - and include links to your bugs in your
ISO test reports.
- If you think a bug has gone unnoticed and should be a higher priority for the
release, try talking to the developers directly on IRC (#ubuntu-devel on
irc.freenode.net).
- Yes, a dfferent bug summary might also have helped. E.g., discussing the
high-level consequence of the bug, as was done in bug #462961.
Hope that helps - it obviously would have been better if we could have
fixed this bug weeks earlier when you first noticed it!
--
os-prober entries do not use correct /boot device
https://bugs.launchpad.net/bugs/445367
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
