As the stable releases become first class citizens, we should probably look at streamlining the process of getting patches to them.
The maintainer for the stable release currently changes by release, which undoubtedly creates some confusion of where to send patches and who to CC. These maintainers currently attempt to track these patches via email filters searching for release branch names and such, which is proving tedious and prone to missing patches. Other projects have seen good results using a stable list for this purpose. This would both make it obvious when a patch is intended for a stable release as well as remove any confusion about who to Cc as it would be the same list for all releases. Perhaps something like [email protected]? In addition to the list, some policy would need to be documented on how to use the list. For example, it should always be Cc'd, and never emailed with patches directly that don't go first to the master branch. Backports being the exception. A policy could also be put in place to aid in automatic processing, such as that employed by the Linux kernel stable project. The following would request that the patch be applied to the denzil and danny stable releases: Cc: <[email protected]> # denzil Cc: <[email protected]> # danny Signed-off-by: Darren Hart <[email protected]> The advantage here over something like a subject tag, "[danny]" is that it scales a bit better to sending a patch for multiple releases. There are certainly other approaches, I mention this one as it has a proven track record and I don't have a reason to deviate from it. Thoughts? -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
