Hi, I was thinking how we could make tracking bugfixes for release branches easier. I see nothing fundamentally wrong with the Linux stable tree workflow. It is as most linux kernel things email based and works by adding a 'CC: [email protected]' line to the commit message.
The email address should be in our case either a mailing list tracked by patchwork or a email address which feeds patches into patchwork. The commit hook of the git server will CC that address on the commit notification message. If the CC:-line was forgotten the commit email can still be bounced later to the address. Patchwork is unfortunately not an ideal fit for this purpose. The post commit hook will mark patches as committed when they are pushed to a single release branch although they might need to go into more than one branch. Or it will miss it completely when the backport changed the commit too much. While this is far from a perfect solution it is imho a worthwhile improvement over the current situation. Has anyone a better idea? Objections? I'll do of course the infrastructure work. I've created a snapshot of fate-suite for Libav 0.8. It is available as http://fate-suite.libav.org/fate-suite-0.8/ or rsync://fate-suite.libav.org/fate-suite-0.8/ Backward incompatible changes to fate-suite are rare but not unknown. I'm still contemplating if a patch for the 0.8 release branch changing the url of the fate-rsync rule is helpful or not. I guess it needs at least documentation that the release branch needs a different SAMPLES location. Fate-suite-0.8 won't need much additional space if copied using hard links. Janne _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
