On Tue, 2016-07-19 at 15:40 +0200, Goswin von Brederlow wrote: > On Mon, Jul 18, 2016 at 07:41:54PM +0200, Andreas Metzler wrote: [...] > > Testing has 2016.0.0+dfsg-1, which was followed by > > [2016-07-16] 2016.2.0~rc1+dfsg-2 in unstable (low) > > [2016-07-11] 2016.2.0~rc1+dfsg-1 in experimental (low) > > [2016-06-04] 2016.2.0~beta1+dfsg-1 in experimental (medium) > > > > britney seems to have remembered that 2016.2.0~beta1+dfsg-1 had medium > > urgency and chose to consider this urgency for sid->testing migration. [...] > Does it remember or does it parse the changelog and use the highest > priority since the version in testing? The hugin changelog contains > the urgency=medium entry so this seems a valid urgency to use.
britney knows nothing about changelogs. The input is a strictly chronological (in terms of when dak accepted the package) list of source package name, version and urgency tuples for all uploads to the main archive. Regards, Adam
