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
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.
-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
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
-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:
-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
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-
-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.
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
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
(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
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
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
-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
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
15 matches
Mail list logo
