305297 - No mozilla trunk source tarballs being generated / staged since SeaMonkey changes landed

Status: RESOLVED FIXED

(mozilla.org :: FTP: Staging, task)

Description

[Ian Neal]

Since the new build changes to create SeaMonkey have landed there have been no
source tarballs generated / staged for the trunk. I am presuming they should be
appearing under the seamonkey directory structure but I suppose the alternative
is under it's original place, the mozilla directory structure.
It would be good to get this working again so people can more easily set up new
build environments and not have to pull the whole tree by cvs.

Comment 1

[J. Reynolds]

This is *long* overdue.  Does this need to be reassigned to SeaMonkey Council
people or are we waiting for a SeaMonkey 1.0 branch or what's going on?

Comment 2

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

As far as I know, the SeaMonkey Council doesn't have the power to fix this.

Comment 3

[Robert Kaiser]

No, that's completely MoFo's thing, either zach or Chase need to look into egg
creating and uploading tarballs somewhere again.

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

(this issue was previously discussed in bug 298901)

Comment 5

[Zach Lipton [:zach]]

The policy issues with this need to be worked out with staff before I can create
accounts. I have an email into Asa on the subject, and we'll go from there...

Comment 6

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

(In reply to comment #5)
> The policy issues with this need to be worked out with staff before I can create
> accounts. I have an email into Asa on the subject, and we'll go from there...

Zach, I don't think source tarballs are related to builds.

Comment 7

[Zach Lipton [:zach]]

Well, they are somewhat related. As part of the discussion, the Council and
staff need to decide what infastructure mozilla.org is going to provide for
Seamonkey use. It appears that m.o will provide a machine that can do this. If
that's the case then this is a build issue and Chase can take care of it. If
it's being done externally, then we need to figure out who is going to do that
and get them an account. 

Comment 8

[Asa Dotzler [:asa]]

We intend, at Mozilla, to support the Seamonkey effort as best we can. During
release time at Mozilla, we're stretched extremely thin and all other projects
take a back seat to Firefox and Thunderbird.

Chase is only one person and there are only so many hours in the day. If there
is a build expert on the Seamonkey team that wants to do the work that Chase
can't (right now) then we should work out the details to get that Seamonkey
build person the necessary access to fill in when Chase is otherly occupied.

If that person doesn't exist, then we wait on Chase to get some free time.

Comment 9

[Chase Phillips]

The source tarball is being uploaded again.