[Piglit] [RFC] Piglit tags/releases

Matt Turner mattst88 at gmail.com
Mon Sep 29 10:01:59 PDT 2014

On Mon, Sep 29, 2014 at 9:34 AM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> While I've been through the RELEASES document I believe it would be
> beneficial if we regularly create a tag("release"), that is to serve the
> following
>  - Human understandable format
> I.e. version 1.0.2 comes after 1.0.1, oh there is even date in there.

See next point.

>  - Something everyone can parse, unlike b33979a8f5c852fbffc072b0.
> When you don't have the tree at hand or don't know what git is.

If either of these is the case, you have no business with piglit.

>  - Ease distributions interested in packaging piglit.

I don't see value in distributions packaging piglit.

>  - Something for our QA and other non-developer teams to cling onto.

I think this has actually back fired for us when we tried. Ian
probably remembers more.

More information about the Piglit mailing list