Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
On Mon, 2005-05-16 at 20:17 -0400, Jeffrey Forman wrote: The upgrade for bugs.gentoo.org went exactly as I had planned for. Completed in under 20 minutes, which included this email. I've upgraded our Bugzilla from the old 2.18rc2 to 2.18.1. This fixes more security and code than I can even begin to mention. I have cleaned out a lot of the code and added in some nice features. Thank you so much for working on this, Jeffrey - I really appreciate it. Nice to see that the upgrade went smoothly too. Those nice features I'd like to higlight: (1) In the bug list, enhancements are colored green, while critical and blocker bugs are still colored red. This should help in picking out the enhancement bugs. While color coding is good, I think it would be nice (at least from an accessibility point of view) to still have enhancement requests written in italics. (4) Comments now have [reply] links where clicking, will append the reply into the 'Additional Comments' textbox where one can easily comment on earlier replies. That's the most useful new feature in this release, if you ask me. (5) Strikeouts now work for bugs with closed-like resolutions. Allows a user to more quickly tell the status of a resolved bug. This is nice too, been missing that functionality. Anything else I've forgotten, I will happily take full credit for. I would also like to thank the numerous bugzilla developers over in irc.mozilla.org in #mozwebtools. They were endlessly patient with my questions and I am endlessly greatful. Thank you to all who made the upgrade possible and smooth (at least it was smooth for me ;) Sincerely, Brix -- Henrik Brix Andersen [EMAIL PROTECTED] Gentoo Linux signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
iawww, i thought that added extra emphasis to the post history... ;) On Monday 16 May 2005 08:41 pm, Jeffrey Forman wrote: Good eye, Fixed! -Jeffrey On Tue, 2005-05-17 at 09:25 +0900, Georgi Georgiev wrote: Something's wrong with the i tags -- the one before Additional is never closed. span class=bz_comment --- iAdditional Comment a name=c2 href=#c2#2/a From !-- JSF - unfangled all the emails, so they are spam spider unfriendly -- iBrandon Low/i 2002-03-07 15:57 PDT --- /span Thus all comments show up as italic. -- -o()o- Michael Cummings |#gentoo-dev, #gentoo-perl Gentoo Perl Dev|on irc.freenode.net -o()o- pgpKhAYRVQffU.pgp Description: PGP signature
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan Smith wrote: I noticed a bug [1] which, when resolved after the upgrade, did not list the cause of resolution (in this case, it was a dup). Is this no longer required? I rather liked that feature, as it enabled people to see, at a quick glance, the final status of the bug... [1]: https://bugs.gentoo.org/show_bug.cgi?id=92861 smithj, the bug showed that information for me: Clear-Text: http://bugs.gentoo.org/show_bug.cgi?id=92861 Secure: https://bugs.gentoo.org/show_bug.cgi?id=92861 [EMAIL PROTECTED] changed: What|Removed |Added - Status|NEW |RESOLVED --- Additional Comments From [EMAIL PROTECTED] 2005-05-17 01:46 PDT - --- *** This bug has been marked as a duplicate of 12745 *** Here it is, the last row. - -- Alin DOBRE Romanian Lead Translator Gentoo Documentation Project: http://www.gentoo.org/doc/en/ Gentoo.RO Community: http://www.gentoo.ro/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCievUmG51ym6Hu9gRAqRTAKCB3yMPL3wxtKN0khWG2omYvVni1ACg1uEK JDERrmlt3ojv78yNkOAs8dA= =5TVL -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
maillog: 17/05/2005-16:04:20(+0300): Alin Dobre types -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan Smith wrote: I noticed a bug [1] which, when resolved after the upgrade, did not list the cause of resolution (in this case, it was a dup). Is this no longer required? I rather liked that feature, as it enabled people to see, at a quick glance, the final status of the bug... [1]: https://bugs.gentoo.org/show_bug.cgi?id=92861 smithj, the bug showed that information for me: Clear-Text: http://bugs.gentoo.org/show_bug.cgi?id=92861 Secure: https://bugs.gentoo.org/show_bug.cgi?id=92861 [EMAIL PROTECTED] changed: What|Removed |Added - Status|NEW |RESOLVED --- Additional Comments From [EMAIL PROTECTED] 2005-05-17 01:46 PDT - --- *** This bug has been marked as a duplicate of 12745 *** Here it is, the last row. But in the headers it says: Status: RESOLVED Resolution: -- -* Georgi Georgiev -* Humor in th Court: Q: Do you drink when -* *-[EMAIL PROTECTED]*- you're on duty? A: I don't drink when I'm*- -* +81(90)2877-8845 -* on duty, unless I come on duty drunk.-* -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan Smith wrote: Georgi Georgiev wrote: maillog: 17/05/2005-16:04:20(+0300): Alin Dobre types *** This bug has been marked as a duplicate of 12745 *** Here it is, the last row. But in the headers it says: Status: RESOLVED Resolution: right. what i was saying was that it is very nice to see the reason for resolution in the summary section. something like this: What|Removed |Added - Status|NEW |RESOLVED Resolution||DUPLICATE yes, indeed, the Resolution is empty, now. - -- Alin DOBRE Romanian Lead Translator Gentoo Documentation Project: http://www.gentoo.org/doc/en/ Gentoo.RO Community: http://www.gentoo.ro/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCifotmG51ym6Hu9gRAiYbAJ9FHjkNFnQxJhN9KHCxHT8mAaAQvwCfQsD0 Tr8LMuYW3M/X1CQflOgH9+s= =xT1h -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey Forman wrote: [snip] Anything else I've forgotten, I will happily take full credit for. [snip] one more thing: comment #15 of bug 92622 [1] shows the bug which was a dup as marked through. perhaps this is intentional (resolved bugs show this attribute?), but it is very annoying, and it makes it hard to see the bug number without clicking on it to go to the link. sorry for the deluge of posts. overall, though, i very much like the new bugzilla, so don't take my comments the wrong way ;-) [1]: https://bugs.gentoo.org/show_bug.cgi?id=92622#c15 - -smithj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCifwTl5AvwDPiUowRApkRAJ97dCUnzHTtsTUVDeVMn+Qcx5FRywCgtEF0 St9KDsjnf15mfRUD08MJdDs= =xS1I -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
I've looked at the actual DB behind bugzilla, and that seems to be the only bug having that such situation, with a resolved-like status, but no resolution, all the other bugs look fine. *shrug* -Jeffrey On Tue, 2005-05-17 at 17:05 +0300, Alin Dobre wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan Smith wrote: Georgi Georgiev wrote: maillog: 17/05/2005-16:04:20(+0300): Alin Dobre types *** This bug has been marked as a duplicate of 12745 *** Here it is, the last row. But in the headers it says: Status: RESOLVED Resolution: right. what i was saying was that it is very nice to see the reason for resolution in the summary section. something like this: What|Removed |Added - Status|NEW |RESOLVED Resolution||DUPLICATE yes, indeed, the Resolution is empty, now. -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey Forman wrote: That seems odd, then again, those are VERY old bugs. Way before my time of looking at bugzilla to upgrade. Don't think it has anything to do with age. Just marked this one a dup this morning. http://bugs.gentoo.org/show_bug.cgi?id=92539 - -- Power, n.: The only narcotic regulated by the SEC instead of the FDA. Aaron Walker [EMAIL PROTECTED] [ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCigtuC3poscuANHARAvAcAKDeyDCkDFbQQgFpYQujD386cNiEjwCdEi5O j7wOcgkhAIesatP2kckZTYo= =5Pz/ -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
Bingo, I found the correlation between those bugs and the previous ones mentioned by Daniel. They have all been marked as duplicates of other bugs. Therefore bugzilla does not put a resolution in there, only marking them as status: resolved. -Jeffrey On Tue, 2005-05-17 at 11:19 -0400, Aaron Walker wrote: Jeffrey Forman wrote: That seems odd, then again, those are VERY old bugs. Way before my time of looking at bugzilla to upgrade. Don't think it has anything to do with age. Just marked this one a dup this morning. http://bugs.gentoo.org/show_bug.cgi?id=92539 -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
I retract my earlier statement. In the upgrade, I forgot to fully copy over all the resolution states. (Don't you just love that comfortable feeling that comes with editing a live system?) Now when a bug is marked as a duplicate it shows up as Status: RESOLVED Resolution: DUPLICATE of bug (some other bug #) Sorry for the confusion, I sit corrected. -Jeffrey On Tue, 2005-05-17 at 11:47 -0400, Jeffrey Forman wrote: Bingo, I found the correlation between those bugs and the previous ones mentioned by Daniel. They have all been marked as duplicates of other bugs. Therefore bugzilla does not put a resolution in there, only marking them as status: resolved. -Jeffrey -- Jeffrey Forman Gentoo Infrastructure Gentoo Release Engineering [EMAIL PROTECTED] -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
(fearing the jeff wrath) can we get the dup status added back in though? i know, i know, we're being nitpicky, and not too many folks have stood up and applauded this effort like they should have (ahem). Just...unsettling to see bugs marked as resolved - make it sound like i did something rather than find that the same problem had been reported a few times :) On Tuesday 17 May 2005 11:47 am, Jeffrey Forman wrote: Bingo, I found the correlation between those bugs and the previous ones mentioned by Daniel. They have all been marked as duplicates of other bugs. Therefore bugzilla does not put a resolution in there, only marking them as status: resolved. -Jeffrey On Tue, 2005-05-17 at 11:19 -0400, Aaron Walker wrote: Jeffrey Forman wrote: That seems odd, then again, those are VERY old bugs. Way before my time of looking at bugzilla to upgrade. Don't think it has anything to do with age. Just marked this one a dup this morning. http://bugs.gentoo.org/show_bug.cgi?id=92539 -- -o()o- Michael Cummings |#gentoo-dev, #gentoo-perl Gentoo Perl Dev|on irc.freenode.net -o()o- pgpx5fBJYOfLE.pgp Description: PGP signature
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
Michael, You are very welcome, it was a pleasure to upgrade such a critical piece of Gentoo, even though it required time I could have spent outside in the Florida sun. As for your question about adding in the duplicate status. 'Duplicate' isn't a status, its a resolution state. I point you to http://bugs.gentoo.org/page.cgi?id=fields.html#status for a better explanation. So in a more abstract sense, a Duplicate bug has been 'resolved,' as someone has determined that it is a duplicate bug and pointed the bug to its appropriate original filing. With that said, I put this issue to rest. ;) Yes, it's nitpicky, but I won't impart any bodily harm on you. -Jeffrey On Tue, 2005-05-17 at 12:42 -0400, Michael Cummings wrote: (fearing the jeff wrath) can we get the dup status added back in though? i know, i know, we're being nitpicky, and not too many folks have stood up and applauded this effort like they should have (ahem). Just...unsettling to see bugs marked as resolved - make it sound like i did something rather than find that the same problem had been reported a few times :) -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
yeah, i hit send, then jforman hit send. sorry. On Tuesday 17 May 2005 12:42 pm, Michael Cummings wrote: (fearing the jeff wrath) can we get the dup status added back in though? i know, i know, we're being nitpicky, and not too many folks have stood up and applauded this effort like they should have (ahem). Just...unsettling to see bugs marked as resolved - make it sound like i did something rather than find that the same problem had been reported a few times :) On Tuesday 17 May 2005 11:47 am, Jeffrey Forman wrote: Bingo, I found the correlation between those bugs and the previous ones mentioned by Daniel. They have all been marked as duplicates of other bugs. Therefore bugzilla does not put a resolution in there, only marking them as status: resolved. -Jeffrey On Tue, 2005-05-17 at 11:19 -0400, Aaron Walker wrote: Jeffrey Forman wrote: That seems odd, then again, those are VERY old bugs. Way before my time of looking at bugzilla to upgrade. Don't think it has anything to do with age. Just marked this one a dup this morning. http://bugs.gentoo.org/show_bug.cgi?id=92539 -- -o()o- Michael Cummings |#gentoo-dev, #gentoo-perl Gentoo Perl Dev|on irc.freenode.net -o()o- pgp15yEBzFG0R.pgp Description: PGP signature
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey Forman wrote: You are very welcome, it was a pleasure to upgrade such a critical piece of Gentoo, even though it required time I could have spent outside in the Florida sun. Heh, that explains why I spend so much time working on Gentoo -- this rainy Oregon weather. =) Some of the new features are pretty sweet though, so thanks for doing it! Donnie -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCiiugXVaO67S1rtsRAgbkAKCZmu66b2OkwZUY/MjlXr6elG2zoACfQaMO hkSrMrWa7517hNMgSKxj+5Q= =2tFV -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] UPGRADE complete bugs.gentoo.org
Donnie Berkholz wrote: Some of the new features are pretty sweet though, so thanks for doing it! Is it possible to add some feature which will allow end users to change timezone in which the times are reported? Or at least allow UTC? -jkt -- cd /local/pub more beer /dev/mouth signature.asc Description: OpenPGP digital signature
