> > > Now, since we maintain task-dockerautotest, it should go into
> > > qa.*,
> >
> > Agreed. Once we have dist-git checks implemented, we can ask docker
> > maintainers to keep it and maintain it in their repo. If they don't
> > want, we can keep it in our domain (same as anyone will be able
On Thu, 2 Jun 2016 07:46:33 -0400 (EDT)
Kamil Paral <kpa...@redhat.com> wrote:
> > Hi,
> >
> > we have deployed task result namespaces support a while ago and put
> > our checks (depcheck, upgradepath, rpmlint) into the 'qa' namespace.
> > With newly add
> Hi,
>
> we have deployed task result namespaces support a while ago and put
> our checks (depcheck, upgradepath, rpmlint) into the 'qa' namespace.
> With newly added tasks like task-abicheck and task-dockerautotest,
> we weren't sure where to put them and so we used the s
Hi,
we have deployed task result namespaces support a while ago and put
our checks (depcheck, upgradepath, rpmlint) into the 'qa' namespace.
With newly added tasks like task-abicheck and task-dockerautotest,
we weren't sure where to put them and so we used the scratch
namespace which is supposed
