Closed Bug 298901 Opened 19 years ago Closed 19 years ago

Move staging for SeaMonkey to new FTP directory

Categories

(SeaMonkey :: Build Config, defect)

Product:
SeaMonkey
Component:
Build Config
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
seamonkey1.0alpha

People

(Reporter: kairo, Assigned: chase)

References

(
URL
)

Details

Another infrastructure change to go along with rebranding (bug 285696) is moving
staging of new SeaMonkey-branded nightlies to their own directory on stage/FTP.

The tinderbox changes needed to place builds there can be done along with bug
289846.

For the stage changes, I already have an account there (kairo), so if there's a
new group made that has write permissions to /data/ftp/pub/seamonkey/ please
make me a member of that one as well. The subdirectory structure under that dir
should bascially be like e.g. the firefox one.
Flags: blocking-seamonkey1.0a+
Target Milestone: --- → Seamonkey1.0alpha
Chase, just as a note:
The real rebranding patch is up at bug 285696 and should have reviews soon.
This means, it will hopefully be able to land soon (meaning that I'd like it to
happen before 1.8b3) in a concerted effort with bug 292268 and bug 288199.

This comment is meant as a warning that those infrastructure issues might get
hot within a week or so. Stage can probably be prepared before that, tinderboxen
have to be fixed after the fact anyways.
OK, we're ready to go code/patch-wise, but Chase is overloaded currently (no
time before the july 4 holiday) and can't do the infrastructure stuff atm.

We have to coordinate bugs 292268,285696,288199,289846,298901 to make it all
happen at once and make the transition as smooth as possible, so we'll push out
the whole thing a few days (this is all SeaMonkey-only so we don't have to care
about aviary 1.1a2 too much), I hope it'll be ASAP - still need to schedule an
impact date/time with Chase though.

Additionally, we'll have to wait a few days as well to get MoFo reviews on the
announcement which should go public in a tight timeframe around the happening of
those changes.
Please be warned it's coming up but patient at the same time.
OK, this is bascially done, according to Chase only egg has to be adjusted to
deliver source tarballs to the new directory as well.
URL: http://ftp.mozilla.org/pub/mozilla.or...
(In reply to comment #3)
> OK, this is bascially done, according to Chase only egg has to be adjusted to
> deliver source tarballs to the new directory as well.

see bug 302043 for that

*** Bug 302043 has been marked as a duplicate of this bug. ***
I just got word that the source tarball issue is blocking e.g. Gentoo from
making our application available to their users. I'd hope we would get that
resolved so that we get more testers of the code...
(In reply to comment #6)
> I just got word that the source tarball issue is blocking e.g. Gentoo from
> making our application available to their users. I'd hope we would get that
> resolved so that we get more testers of the code...

Can you enlighten me on this?  As far as I know egg doesn't produce source for
Firefox on a nightly basis.  What directories and files are missing from the
mozilla-source tarball in mozilla/ that blocks Gentoo?
(In reply to comment #8)
> well the source tarball in
> ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest hasn't been updated
> in a month...

My migraine just got a little bigger.
(In reply to comment #9)
> (In reply to comment #8)
> > well the source tarball in
> > ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest hasn't been updated
> > in a month...
> 
> My migraine just got a little bigger.


Actually, the real issue is that we have no tarballs at all at the moment, I
wouldn't care that much where it is placed (as long as people find it) - but we
really should have a tarball available that has all the source to do a current
suite build...
OK, closing this as FIXED. The mozilla tarball issue is filed as bug 305297
anyways, and everything else is fixed for now.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.