Scott,
On Jan. 19, well before the feature freeze, a bug report was filed
to bring git 1.6.0.4 to 1.6.0.6 to fix bugs and the patch to do so was
even provided. You had some initial issues with the patch, but after
they were addressed you assigned yourself to the bug report on Jan. 20.
Then you decided to wait until after the feature freeze to say
"None of these bugs seem severe enough to warrant breaking... Feature
Freeze".
Scott, is it standard practice for member's of Ubuntu's technical board
to assign themselves to bugs with patches submitted over a month before
the feature freeze then wait until after the feature freeze and say
"sorry, can't fix bugs after the feature freeze." Perhaps this is why
Ubuntu has so many un-fulfilled confirmed bug reports.
Please:
1. Don't assign yourself to bugs of packages you have a public disdain
for [1] if you won't patch them.
2. Don't assign yourself to bugs with a patch, then wait until after
feature freeze to say "sorry, it's now too late."
PS. To be fair, most other Ubuntu developers do upload your patches
when you get patches into the form they request when submitted a month
before the feature freeze.
[1] http://www.netsplit.com/2009/02/17/git-sucks/
--
Please upgrade git-core to 1.6.2
https://bugs.launchpad.net/bugs/319096
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
