[Skiboot] stable trees and process
andrew.donnellan at au1.ibm.com
Fri May 25 11:49:43 AEST 2018
On 25/05/18 11:39, Stewart Smith wrote:
> Hey all,
> So, we do major releases and have stable trees, with some specified
> process around doing stable (see
> https://open-power.github.io/skiboot/doc/stable-skiboot-rules.html ).
> Although the *reality* has been a bit more ad-hoc, with candidates for
> stable being from either me talking to people on email, slack or in
> (often IBM-internal) bug reports.
> I'd like to change that, and have us follow the above process.
> That is, *use* the "CC: stable" tag when a fix needs to get to a stable
> So, if a patch needs to get to a service pack for an IBM firmware
> release, it needs to get into a stable tree. (the same is probably also
> true for other openpower system vendors)
Pro tip, because I've done this several times, don't add "Cc: stable" to
your skiboot patch, and then by the magic of git send-email with a
mailrc configured, accidentally have that turn into a Cc to
stable at vger.kernel.org...
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan at au1.ibm.com IBM Australia Limited
More information about the Skiboot