Build page is a mess in the 1.0 layout

[Matthew Paul Thomas]

Build pages, such as <https://beta.launchpad.net/+builds/+build/276173/pbuilder>, are a mess in the 1.0 layout. There are no tabs, which causes the content area to begin too high, which in turn chops off part of the search field. And the top left of the page says "No structural object".

This bug was prefigured in bug 31622, where I said: "a build page should belong to the source package it's built from. For example, <https://launchpad.net/+builds/+build/169627> would have the hierarchy Launchpad > Distributions > Ubuntu > banshee." Doing that would solve the layout problems here, and make build pages look less like orphans. It would also (if the URL scheme was changed to make build pages descendants of source package pages) abolish the "/+builds/+build/" wackiness that I carelessly specced in 2005.

[Celso Providelo (cprov)]

Mark has suggested that +builds becomes "Code" contents for Distrobution/DistroRelease/DistroArchRelease and related.
This should sort half of the issue Matthew has pointed.
We haven't found a solution for '+builds' on LP root (the Builders and its childs) yet.

[Matthew Paul Thomas (mpt)]

I don't think that would be understandable. Technically builds are binary code, but they're not Code in the way that term is used everywhere else in Launchpad.

[Celso Providelo (cprov)]

Ok, you may disagree and we can try to find a more reasonable solution, but It doesn't make builds "binary code" :(

I clearly see the analogy: as Branches are "code" for Products, Sources/Builds/Binaries are "code" for Distribution (and children).

But I understand that you would expect to see "Branches for Ubuntu" ... which is not possible right now.

Anyway, suggestions are welcome.

[Matthew Paul Thomas (mpt)]

I still think it would make sense for builds to be underneath their source packages -- or more precisely, under the relevant source package release. So for example, you could drill down through
https://launchpad.net/ubuntu/+source/firefox
https://launchpad.net/ubuntu/+source/firefox/2.0.0.2+1-0ubuntu1 (which already has a portlet with build links)
https://launchpad.net/ubuntu/+source/firefox/2.0.0.2+1-0ubuntu1/+builds/304058
https://launchpad.net/ubuntu/+source/firefox/2.0.0.2+1-0ubuntu1/+builds/304058/firefox-gnome-support

All these pages would have the source package as their context object, so for example clicking the "Bugs" tab on any of them would go to <https://bugs.launchpad.net/ubuntu/+source/firefox>.

[Celso Providelo (cprov)]

Your proposal sounds reasonable.

I'd also suggest that we could link straight to:

https://beta.launchpad.net/ubuntu/feisty/i386/sqcwa/0.3-3

instead of having:

https://beta.launchpad.net/+builds/+build/148670/sqcwa

What do you think ?

[Matthew Paul Thomas (mpt)]

If those pages present exactly the same information in different ways (and it looks like they do), then yes, getting rid of the second one is a great idea.

[Joey Stanford (joey)]

retargeting to 1.1.6

[Julian Edwards (julian-edwards)]

Fixed in RF 4356