370471 - terms on main bonsai page seem outdated, confusing

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations: Projects, task, P3)

Description

[Ray Kiddy]

I would expect to see things like Firefox there, but I do not. Instead I see Grendel.

Perhaps the links and lists in the interface need to be refreshed.

Comment 1

[Dave Miller [:justdave]]

We can set up whatever's needed, but someone needs to decide what to set up first.

This probably involves build folks, too.

Comment 2

[Ray Kiddy]

This should not really be very complicated.

Here is a list:

    1) NSPR, 2) Camino, 3) Bugzilla, 4) Grendel

Which one does not belong? Well, all of them are current projects, except Grendel. Also, some of the items in the list of modules are huge and others are small.

Why not just use the list of buildable products from the build tree, and an "all" target.

This is not a big deal. I am just asking that this page be changed to reflect reality.

Comment 3

[Reed Loden [:reed]]

See bug 375581 for info on Grendel.

Comment 4

[Gervase Markham [:gerv]]

This is still an issue.

I'm sure the server team can think of some appropriate queries to list. Grendel can do, as can Aviary and Mozilla Classic; SeaMonkey probably needs to be renamed "Trunk" or "Mozilla" or something like that.

Just do something sensible and see who complains :-)

Gerv

Comment 5

[Dave Miller [:justdave]]

Bonsai tree names seem to be intricately tied to both CVS modules and Tinderbox trees.  I'd be scared to touch anything (other than perhaps adding new ones) without signoff from build folks for fear of breaking tinderboxes.

Comment 6

[Chris Cooper [:coop] (he/him)]

I'm not sure we need the Firefox moniker in there, but I may be biased by already knowing the what modules correspond to which products. Given that Dave thinks the naming may be fragile, I think we could solve this issue by updating the page header with a basic matrix of Product/Version/Module info, 

e.g. 
Firefox | 1.5.x | SeaMonkey (Mozilla 1.8.0 branch)
Firefox | 2.x   | SeaMonkey (Mozilla 1.8 branch)
etc...

I think we could safely lose the following links (along with any processing that happens for them on the back-end, which is hopefully none):

# SeaMonkey (Mozilla 1.0 branch)
# Mozilla Classic
# Aviary 1.0 Branch
# Aviary 1.0.1 Branch
# Grendel (Java Mail/News)

I'm not sure how "Security Services" differs from NSS. We could potentially lose this too.

Comment 7

[Reed Loden [:reed]]

(In reply to comment #6)
> I'm not sure how "Security Services" differs from NSS. We could potentially
> lose this too.

Security Services contains NSS, JSS, etc. (more than just NSS). It was just recently added, so we shouldn't be touching it at all.

Comment 8

[Chris Cooper [:coop] (he/him)]

Re-assigning to server-ops because I assume someone there (justdave?) has access and can edit the treeconfig.pl file on the bonsai server.

(In reply to comment #6)
> # SeaMonkey (Mozilla 1.0 branch)
> # Mozilla Classic
> # Aviary 1.0 Branch
> # Aviary 1.0.1 Branch
> # Grendel (Java Mail/News)

These can be safely removed. No tinderboxes rely on them.

I can create the patch I suggested for the page header, if people think that would be useful.

Comment 9

[Dave Miller [:justdave]]

I think I'm going to tie this in with the Tinderbox config audit on bug 397298, because of the "fragile naming" issue.  If both of these are done at the same time then it won't matter, because we can change whatever needs changing anyway (a pretty sizable chunk of them appear to be already broken anyway).

Comment 10

[Reed Loden [:reed]]

(In reply to comment #8)
> (In reply to comment #6)
> > # SeaMonkey (Mozilla 1.0 branch)
> > # Mozilla Classic
> > # Aviary 1.0 Branch
> > # Aviary 1.0.1 Branch
> > # Grendel (Java Mail/News)
> 
> These can be safely removed. No tinderboxes rely on them.

They have been removed from @::TreeList in treeconfig.pl. I also renamed "SeaMonkey (Mozilla trunk)" to "SeaMonkey (Mozilla 1.9.0 branch)" since CVS HEAD is now the new 1.9.0 branch.

> I can create the patch I suggested for the page header, if people think that
> would be useful.

I don't think it's really needed, personally. We're using Bonsai less and less with Hg now, so I'm not sure it is worth it. However, if somebody believes it would be helpful, that can be done. Thoughts? If people think the current change was sufficient, I'll close out this bug.

Comment 11

[Reed Loden [:reed]]

Closing this out.