On Mon, 2016-06-13 at 11:41 +0100, Stephen Finucane wrote: > Add support for series. Series are groups of patches sent as one > bundle. For example: > > [PATCH 0/3] A cover letter > [PATCH 1/3] The first patch > [PATCH 2/3] The second patch > [PATCH 3/3] The third patch > > The following features are currently provided: > > Parsing > ======= > > * Creation of new series, and linking of patches/cover letters to > existing series > * Rudimentary linking of different series revisions as one series > > UI > == > > * Series column in patch-list > * Series and related patches/cover letters links in patch-detail > * Filtering by series > * Integration with Django-admin > > There are some important notes regarding how this is implemented: > > * We *never* expose 'Series' to the end-user. Instead, "related > series" should be exposed > * Patches form a one-to-one relationship with SeriesReference. > Auto-completion of series should be done in the view code, rather > than the database
Currently in Patchwork, individual patches can have a reported test state (or a Check, as it's referred to in the docs). I couldn't find anything in this series that affects this, what are your thoughts on moving that functionality from a patch model to a series model? Any kind of tests run on a patch are typically focused on the entire series. _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
