Hi,
On Thu, Nov 03, 2016 at 05:47:17PM +, Mattia Rizzolo wrote:
> This thread doesn't seem to make progress, anyway:
(it was still on my to-reply list…)
> On Tue, Oct 18, 2016 at 09:54:39PM +, Mattia Rizzolo wrote:
> > 4. figure out why the hell DDPO doesn't deal with that edit in the j
This thread doesn't seem to make progress, anyway:
On Tue, Oct 18, 2016 at 09:54:39PM +, Mattia Rizzolo wrote:
> 4. figure out why the hell DDPO doesn't deal with that edit in the json,
>see the code⁵ in Debian's QA Team SVN repo, and leave the json to
>display testing data as it is no
On Wed, Oct 19, 2016 at 03:38:29PM +0100, Chris Lamb wrote:
> (Just out of interest, are the same infrastucture, etc. filters used for
> the opt-in "reproducible → unreproducible" emails we send out?)
no. there the assumption is: the maintainers wants to be notified about
changes.
we just send ou
Stuart Prescott wrote:
> > I read a really good book once that made a very convincing argument that
> > dashboards and metrics become subtly undermined once you introduce
> > exceptions or you make them even slightly opaque.
>
> By way of contrast, warnings on my maintainer dashboard should be ac
On Wed, Oct 19, 2016 at 10:09:29PM +1100, Stuart Prescott wrote:
> (There's also a 5th option -- include the build-path in the definition of
> the build environment in the same way as the version of the compiler and
> various other bits of the build environment are mandated. Then there's
> nothi
>> 2. revert to unstable, but filter out packages tagged
>>captures_build_path and friends (DDPO/tracker will just show no data
>>about those packages)
>
> I read a really good book once that made a very convincing argument that
> dashboards and metrics become subtly undermined once you in
On Wed, Oct 19, 2016 at 09:51:24AM +0100, Chris Lamb wrote:
> That, combined with my preference for simplicity, would actually make me
> advocate for no filtering whatsoever (!)
I'm strongly against pushing _noise_ to 25% of our package maintainers.
--
cheers,
Holger
signature.asc
Des
Hi Mattia,
Thanks for starting this thread.
> 2. revert to unstable, but filter out packages tagged
>captures_build_path and friends (DDPO/tracker will just show no data
>about those packages)
I read a really good book once that made a very convincing argument that
dashboards and metrics
Last night we held a short meeting, where one of the item in agenda was
reproducible-tracker.json¹ and how a recentish commit to jenkins² broke
one of its consumers, namely DDPO; after a bit of a discussion³ I
oh-so-happily volunteered⁴ to bring the issue in ML.
One of the purpose of reproducible-
