Thrashing between updates-testing and updates

[Bruno Wolff III]

On Tue, Mar 02, 2010 at 12:26:35 +0100,
  Kevin Kofler <kevin.kofler at chello.at> wrote:
> 
> We could have the branched compose compose from dist-f13 + dist-f13-updates 
> and move everything which was part of its compose from dist-f13-updates to 
> dist-f13 on completion. That way dist-f13-updates would only contain the 
> stuff that was just pushed and didn't make the daily compose yet, which 
> could be offered as an updates repository.

The problems I am seeing is that the branched repo gets built several hours
apart from the testing repo and I don't get consistent views of package
status. Particularly since the branched repo seems to become available
in my afternoons, I seem to get a version of testing in the morning with
updates dropped from testing that will show up later in the afternoon.
It's really just a minor annoyance for me, so if it's hard to fix it
may not be worth doing. The mirrors that pick stuff up pretty often (for
example the kernel mirrors update several times a day as best as I can
tell) probably could save some churn if the packages were signed with the
same key. (I am not sure if that is true yet; though my understanding is
that there will eventually be one key used to sign any official builds
coming out of koji.)