Closed
Bug 523804
Opened 16 years ago
Closed 16 years ago
Update buildbot and pushlog+tinderbox for comm-1.9.1 branch
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect, P1)
Mozilla Messaging Graveyard
Release Engineering
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: standard8, Assigned: gozer)
References
Details
The tree is closed and we're ready to start pulling comm-1.9.1 on tinderboxes by default.
I've also just realised we need to update http://build.mozillamessaging.com/tinderboxpushlog/?tree=Thunderbird3.0 to get the pushlog from comm-1.9.1 not comm-central.
Comment 1•16 years ago
|
||
oh, for tbpl, the same might be true for SeaMonkey2.0, could that be done at once?
| Assignee | ||
Comment 2•16 years ago
|
||
changeset: 1647:ab594c4e8936
tag: tip
user: Philippe M. Chiasson <gozer@mozillamessaging.com>
date: Thu Oct 22 10:51:56 2009 -0400
summary: Bug 523804 - Switch buildbot to using the new releases/comm-1.9.1 branch
| Assignee | ||
Comment 3•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 4•16 years ago
|
||
(In reply to comment #1)
> oh, for tbpl, the same might be true for SeaMonkey2.0, could that be done at
> once?
What about this? (SM 2.0 needs to be updated too.)
| Assignee | ||
Comment 5•16 years ago
|
||
(In reply to comment #4)
> (In reply to comment #1)
> > oh, for tbpl, the same might be true for SeaMonkey2.0, could that be done at
> > once?
>
> What about this? (SM 2.0 needs to be updated too.)
SeaMonkey 2.0 configuration updated to comm-1.9.1 as well.
You need to log in
before you can comment on or make changes to this bug.
Description
•