[Mesa-dev] Stable release process

[Matt Turner]

A long time ago, patch authors were tasked with cherry-picking their
patches to stable branches. Today we Cc
mesa-stable at lists.freedesktop.org and Emil rebases those patches onto
stable. Cc'ing the list happens even on patches sent for their first
review that are ultimately rejected, creating a lot of noise (and
presumably makes the mailing list less useful).

Initial questions:

Is the mesa-stable@ mailing list useful (other than as a tag in a
committed patch)?

What do "nominated" and "queued" in the stable release candidate
announcements actually mean?

Should driver maintainers cherry-pick patches to stable on their own?

Regardless of the outcome of that question, I think we would the
process would be more transparent and predictable if patches were
incorporated into the branch over time rather than all at once a few
days before the release.