If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Status

()

Core
Web Services
P1
critical
VERIFIED FIXED
15 years ago
14 years ago

People

(Reporter: Doron Rosenberg (IBM), Assigned: John Gaunt (redfive))

Tracking

1.0 Branch
mozilla1.5alpha
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
We need a new keg dude!

Comment 1

15 years ago
Are you requesting a new keg person? Or a new keg? If the latter, you meant to
say "We need a new keg, dude!" You're too drunk. No keg for you.

Comment 2

15 years ago
"normal" severity doesn't come close to describing this bug!
Severity: normal → blocker

Comment 3

15 years ago
WHy is this windoze only?
(Reporter)

Comment 4

15 years ago
true
Severity: blocker → critical
OS: Windows 2000 → All
Priority: -- → P1
Hardware: PC → Sun
Version: Trunk → 1.0 Branch
(Assignee)

Comment 5

15 years ago
accepting and targeting....

I think I can get a fix for this in later today.
Status: NEW → ASSIGNED
Hardware: Sun → All
Target Milestone: --- → mozilla1.5alpha
(Assignee)

Comment 6

15 years ago
Yeah baby! Yeah! Groovy!
Status: ASSIGNED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED

Comment 7

15 years ago
Changing QA contact.

Doron: Do whatever testing necessary and mark this verified ;)
QA Contact: ashishbhatt → doron
Well, I'm not so sure if this is verifiable.  I can honestly say that the keg is
not full (anymore).
(Reporter)

Comment 9

15 years ago
verified drunk.

Status: RESOLVED → VERIFIED

Comment 10

14 years ago
we are getting ready to close the tree for 1.5.  what is the state of this bug?
You need to log in before you can comment on or make changes to this bug.