Closed
Bug 723839
(SM2.8b1)
Opened 13 years ago
Closed 13 years ago
Tracking bug for build and release of SeaMonkey 2.8 Beta 1
Categories
(SeaMonkey :: Release Engineering, defect, P1)
Tracking
(seamonkey2.8+ verified)
RESOLVED
FIXED
People
(Reporter: ewong, Assigned: ewong)
References
()
Details
Attachments
(1 file, 1 obsolete file)
4.70 KB,
patch
|
ewong
:
review+
|
Details | Diff | Splinter Review |
This is a tracking bug for Build and Release of SeaMonkey 2.8 Beta 1
We expect an actual release on 4th February 2012.
![]() |
Assignee | |
Comment 1•13 years ago
|
||
Attachment #594082 -
Flags: review?(bugspam.Callek)
Updated•13 years ago
|
Assignee: nobody → ewong
tracking-seamonkey2.8:
--- → +
Comment 2•13 years ago
|
||
Comment on attachment 594082 [details] [diff] [review]
Update configs for SeaMonkey 2.8 beta1.
>-chatzillaRepoRevision = '48d3ca3f72e4' # 0.9.88 but without the version change.
>+chatzillaRepoRevision = 'CHATZILLA_0_9_88_RELEASE' # 0.9.88 but without the version change.
Nit: lets drop this comment -- doesn't have to be this checkin, but this cycle would be good.
Attachment #594082 -
Flags: review?(bugspam.Callek) → review+
![]() |
Assignee | |
Comment 3•13 years ago
|
||
Fixed nit from Comment #2.
Attachment #594082 -
Attachment is obsolete: true
Attachment #594084 -
Flags: review+
![]() |
Assignee | |
Updated•13 years ago
|
Status: NEW → ASSIGNED
Updated•13 years ago
|
status-seamonkey2.8:
--- → fixed
Comment 4•13 years ago
|
||
Hmm, having been on an older 2.7 beta (2.7b4 probably), I got an update for 2.7b5, but not 2.8b1 today (re-checked multiple times). Is the AUS update step just missing or something broken? FWIW, I'm currently on Linux (32 bit).
[If it's manageable from a releng POV, I vote for somehow including the AUS step in release tracking bugs (setup and/or verification).]
![]() |
Assignee | |
Comment 5•13 years ago
|
||
(In reply to Jens Hatlak (:InvisibleSmiley) from comment #4)
> Hmm, having been on an older 2.7 beta (2.7b4 probably), I got an update for
> 2.7b5, but not 2.8b1 today (re-checked multiple times). Is the AUS update
> step just missing or something broken? FWIW, I'm currently on Linux (32 bit).
>
> [If it's manageable from a releng POV, I vote for somehow including the AUS
> step in release tracking bugs (setup and/or verification).]
It should be ok now. I just checked my 2.6.1 beta and it's upgrading to 2.8b1.
So I'm closing this bug.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
status-seamonkey2.8:
fixed → ---
Resolution: --- → FIXED
![]() |
||
Updated•13 years ago
|
status-seamonkey2.8:
--- → verified
![]() |
Assignee | |
Updated•13 years ago
|
Depends on: SM29-RELNOTE
Updated•13 years ago
|
No longer depends on: SM29-RELNOTE
You need to log in
before you can comment on or make changes to this bug.
Description
•