DA_lpn wrote: > I looked at those steps for an existing bug of mine, but did not "Save > Changes". > > I don't think I _should_ have the authority to close the bug. In fact, it > looks like I can also close someone else's bug. That's great if there > haven't been any problems (nice people and all), but I would think only > developers who commit code changes should have that authority. > > Devs don't have time to look at every bug - we (people who file + work on bugs) have to be trusted to do so. Its not like no one will see the rejection - there's an email list where all bug mail goes, so if its rejected wrongly, it can be caught. Feel free to close it if you think its dealt with. kk > On the flip side: > I reported a bug at apple.com's bug reporter. I say their Software Update > on Mac OSX did not report that Xcode 2.3 was available when I was on Xcode > 2.2. Their developer said it is the intended behavior and closed the bug. > Isn't that a joke? They would not even clarify if it was because Xcode was > a separate install from the base installation. Synaptic reports on > non-Ubuntu specific software and Apple can't report on their own software? > Needless to say, it was a frustrating conversation with my hands tied. > > An example of too open versus too closed.
-- Dapper RC freeze during update https://launchpad.net/bugs/46844 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
