PPA page should re-assure the user that their binary packages are being published

I like this a lot. It should be really easy to do as well.

Easy ... except by the fact that there is not BPPH (the record presented as each binary) until the publication has happened.

So, before you start, bear in mind that it won't be a simple TAL-only change.

PENDING -> PUBLISH is a small slot (<= 2 min), compared to the BUILT -> PENDING one (<= 20 min).

This bug is important to fix for the security P3A -- our scripts expect to check for "built" to mean that all binaries are done and present in the PPA archive URL list. This could turn into a nasty race condition, and I happened to notice it today while waiting for intrepid's base-files update to get built. Can we raise the priority of this?

We'll review this today and try and plan it in to our schedules. I'll let you know.

Cheers

Did it manage to make the schedule?

This is also desired by the OEM Services Group.

IMO, we should not suppress the links to the binaries, as it was originally suggested. I say that because the deb files would be already available for download (and installation using gdebi), it would be a pity if we block users interested in this use case.

The UI fixing would include introducing a intermediate icon before the green-check, representing the status a 'this source publishing has built binaries that are not yet published', and listing the corresponding binary package upload status besides the builds (in the hidden area) as we do for ubuntu packages.

{{{
-------------------------------------------------------------
    foo-bar 1.0 Published dapper (?)
-------------------------------------------------------------
...
Builds

i386 (Done)
amd64 (Accepted)
lpia (Done)

Download files from librarian

foo_bar_1.0.tar.gz (5 KiB)
foo_bar_1.0.dsc (2 KiB)
foo_bar_1.0_i386.deb (3 KiB)
foo_bar_1.0_amd64.deb (3 KiB)
foo_bar_1.0_lpia.deb (3 KiB)
-------------------------------------------------------------
}}}

You can see the source publication has binaries that are not yet published, when you expand the row below you can see that the amd64 binaries are not yet published, and finally, you can still download the deb if you need it.

As I said the time-window in which publications are submitted to the 'has binaries pending publication' status can also be reduced, but it will never be instantaneous.

Celso, you said "PENDING -> PUBLISH is a small slot (<= 2 min), compared to the BUILT -> PENDING one (<= 20 min).". Are you saying that it takes less than 2 minutes for binaries to be published after being built? If so, I find that it can actually take up to 20 minutes or more.

Cody,

No, that's not what I've said.

Once BUILT, binaries have to wait up 20 minutes to become PENDING (at this point they appear in the UI, in the expandable area) then a shorter interval (let's say 2 minutes) to become PUBLISHED and show up in the repository.

Does it make more sense now ?

Yup. Thanks for clarifying.

RF8283.

Adds an intermediate state FULLYBUILT_PENDING to the UI which is indicated in the UI by a glowing icon (new icons coming soon).

The expandable section will also reflect this state for individual builds, but is not yet refreshed via ajax as the status summary is (see bug 366042).

Sorry, that should be RF8288 (I mistook the revno it was ec2tested with for the rev number that it landed in RF with).

This was released, but had some associated performance issues that needed patching. Looking into it now.