Closed
Bug 614010
Opened 15 years ago
Closed 15 years ago
upload comm-central bundles weekly
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: dustin, Assigned: jhopkins)
References
Details
Similar to bug 437482, but the MDN page (https://developer.mozilla.org/En/Developer_Guide/Source_Code/Mercurial) also mentions comm-central, so we should probably bundle that, too.
| Reporter | ||
Updated•15 years ago
|
Assignee: dustin → nobody
| Reporter | ||
Comment 1•15 years ago
|
||
gozer, if you're interested in this, the config should be pretty similar to what we did with firefox. If you're not interested, close the bug :)
Assignee: nobody → gozer
Updated•15 years ago
|
Assignee: gozer → john.hopkins
Comment 3•15 years ago
|
||
gozer, since SeaMonkey uses the generateCCBranchObjects I plan on doing this for us so it might be simpler to copy over to the thunderbird/bundles folder what we end up uploading on your end, since the change for us is a simple config flip.
Unless you think placing this in a common folder is better?
Comment 4•15 years ago
|
||
(In reply to comment #3)
> gozer, since SeaMonkey uses the generateCCBranchObjects I plan on doing this
> for us so it might be simpler to copy over to the thunderbird/bundles folder
> what we end up uploading on your end, since the change for us is a simple
> config flip.
Do you have a bug for this on your end ?
> Unless you think placing this in a common folder is better?
Nah, and even though we could just copy the bundles over from you, it would make us dependent on your end completing successfully.
I would prefer if we just independently generated these. Even if it ends up wasting a little bit of disk space every week, should be minimal.
Comment 5•15 years ago
|
||
(In reply to comment #4)
> (In reply to comment #3)
> > gozer, since SeaMonkey uses the generateCCBranchObjects I plan on doing this
> > for us so it might be simpler to copy over to the thunderbird/bundles folder
> > what we end up uploading on your end, since the change for us is a simple
> > config flip.
>
> Do you have a bug for this on your end ?
Bug 631126
> > Unless you think placing this in a common folder is better?
>
> Nah, and even though we could just copy the bundles over from you, it would
> make us dependent on your end completing successfully.
>
> I would prefer if we just independently generated these. Even if it ends up
> wasting a little bit of disk space every week, should be minimal.
If you are doing it on your end, willing to just copy to our folder while you are at it, rather than having our [limited] machines duplicate work?
| Assignee | ||
Comment 6•15 years ago
|
||
Fixed in https://hg.mozilla.org/build/buildbot-configs/rev/8e3f312726b9
Callek has symlinked comm-central.hg so no need to do a separate upload.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 8•15 years ago
|
||
I downloaded and successfully unbundled
"comm-central.hg 28924 KB 05/02/2011 03:06:00"
V.Fixed
***
> (https://developer.mozilla.org/En/Developer_Guide/Source_Code/Mercurial)
I updated this page to include a direct link to (TB) comm-central.hg.
*****
What about doing the same for comm-1.9.2 and comm-1.9.1?
Status: RESOLVED → VERIFIED
| Assignee | ||
Comment 9•15 years ago
|
||
Serge: bug 633254 created to track your request
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•