]> git.ipfire.org Git - thirdparty/patchwork.git/commit
projects / thirdparty / patchwork.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0c7d45e) | patch
docs: Document backport criteria
authorStephen Finucane <stephen@that.guru>
Tue, 14 May 2019 14:56:53 +0000 (15:56 +0100)
committerStephen Finucane <stephen@that.guru>
Fri, 24 May 2019 14:49:21 +0000 (15:49 +0100)
commit8c8b4b96a251deed6a48349e29e6043d2903daec
treee583dfad1ec66940b692a10f6121a3c9ddf98b18tree | snapshot
parent0c7d45e35fe409dd056ccc4558808a8e97ffaf0ecommit | diff
docs: Document backport criteria

Explain why we don't want to be in the business of backport certain
patches, in the long run. It took me a while to put this into words but
I was helped by a similar discussion ongoing in the OpenStack community
at the moment [1].

[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006220.html

Signed-off-by: Stephen Finucane <stephen@that.guru>
Acked-by: Daniel Axtens <dja@axtens.net>
docs/development/releasing.rst diff | blob | blame | history
Mirror of https://github.com/getpatchwork/patchwork.git