Closed Bug 667819 Opened 13 years ago Closed 13 years ago

Push Socorro 2.0 release

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rhelmer, Assigned: jabba)

References

()

Details

(Whiteboard: ETA: 6/30/2011 3:30 PM)

Assignee: server-ops → jdow
I assume we're still holding for a fix on the PG perf regression.
(In reply to comment #0) > URL for build: > https://jenkins.mozilla.org/job/socorro/508/artifact/branch/socorro.tar.gz Sorry testing an 11th-hour fix, will post a new one once it's passed testing. (In reply to comment #1) > I assume we're still holding for a fix on the PG perf regression. Yep bug 665251
> (In reply to comment #1) > > I assume we're still holding for a fix on the PG perf regression. > > Yep bug 665251 Fuzzing found some additional problems we want to investigate further, holding off the release until tomorrow (these only showed up on stage, not on the dev environments).
Just wanted to point out that this can wait until next week if needed - the main thing is to sort out the regressions. We've called the goal done.
Depends on: 665251
Updated ETA in whiteboard and URL field with build to use.
Whiteboard: ETA: TBD → ETA: 6/30/2011 3:30 PM
The source for the build we went with was tagged https://socorro.googlecode.com/svn/tags/releases/2.0_r3263_20110630
we did it.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Thanks for everyone's help. This was definitely a team effort. QA ran the automated battery of tests, manual smoke tested, and the PowerFuzzer. All pass. QA Verified.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.