[PATCH 00/11] Add labels support
dzickus at redhat.com
Fri Sep 14 06:55:05 AEST 2018
On Tue, Sep 11, 2018 at 12:21:26PM -0600, Stephen Finucane wrote:
> > Personally I would *really* like labels to land. They unlock a lot of
> > potential improvements to workflow for maintainers, eg. automated
> > tagging, tagging based on test results etc. As well as finer grained
> > reporting of status to submitters, eg. instead of "new" -> "under
> > review" -> "accepted", I can mark a patch as "under review" and
> > "applied-to-some-branch", then "under review" and
> > "in-testing" etc. etc.
> > Would it simplify (or not?) the implementation if states became a
> > special case of labels?
> Oh, that's a really good idea, actually. The model I had been following
> for the "Remove State" series was to add two new fields to the "Patch"
> model: 'is_open' and 'resolution', the former being a boolean
> open/closed value and the later being an enum of the default state
> fields. I'd be happy to move this entire thing to labels though. Does
> anyone else (Daniel, Don) have thoughts on this?
I would like to see a little more detail on the format of this would look
like. Sorta like how you describe what the data input looks like for 'checks'.
This probably works for us, just want to be sure.
More information about the Patchwork