projects / platform / upstream / mesa.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 46d03d3) | patch
docs: Add my notes on stable-branch patch criteria
authorCarl Worth <cworth@cworth.org>
Thu, 21 Aug 2014 16:46:57 +0000 (09:46 -0700)
committerCarl Worth <cworth@cworth.org>
Thu, 21 Aug 2014 16:46:57 +0000 (09:46 -0700)
commit399b4e2227a79c8a0c025c7e7ca5f4e3832d8dc6
tree5d3680e97b8795719b74122573167133ae191014tree | snapshot
parent46d03d37bf3a75e86f9f8ab56c6a939d04f23383commit | diff
docs: Add my notes on stable-branch patch criteria

This captures the set of rules I have been using for stable-branch management,
(starting with a discussion on the mesa-dev mailing list on July 2013, and
then refined through my own experience of performing stable-branch releases
since then).
docs/devinfo.html diff | blob | history
Domain: Graphics System / GL;