On Mon, 2024-06-17 at 18:18 -0400, Adam Hassick wrote: > Signed-off-by: Adam Hassick <ahass...@iol.unh.edu>
Again, potentially needs updates based on the depends-on discussions. Also, there's a small typo. Address both and I'm good. > --- > ...-series-dependencies-6696458586e795c7.yaml | 20 +++++++++++++++++++ > 1 file changed, 20 insertions(+) > create mode 100644 > releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml > > diff --git a/releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml > b/releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml > new file mode 100644 > index 0000000..ad7cfda > --- /dev/null > +++ b/releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml > @@ -0,0 +1,20 @@ > +--- > +features: > + - | > + Series may now depend on eachother. Patchwork clients may use this s/eachother/each other/ > + information to download and apply the dependencies when applying a > series. > + This dependency relationship is shallow; the dependencies of a dependency > + should not be applied. Multiple dependencies are allowed. The order they > + are applied in is the order they appear in the content from top to > bottom. > + - | > + Patchwork will now look for "Depends-on" entries when parsing mails. > + This may be done by referring to a patch or series ID in the commit > message > + of a patch or the cover letter content: > + ``Depends-on: patch-1234`` or ``Depends-on: series-5678`` > + Alternatively, the web URL of the patch or series may be given: > + ``Depends-on: > http://patchwork.example.com/project/test/list?series=1111`` > + This feature is disabled by default, and may be enabled by adding > + ``ENABLE_DEPENDS_ON_PARSING=True`` to the settings.py. > +api: > + - The API version has been updated to v1.4. > + - Add the "dependencies" and "dependents" fields to the series detail view. _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
