On 26/10/15 09:27, Peter Maydell wrote: > On 26 October 2015 at 06:25, Peter Crosthwaite > <crosthwaitepe...@gmail.com> wrote: >> On Thu, Oct 22, 2015 at 3:30 AM, Peter Maydell <peter.mayd...@linaro.org> >> wrote: >>> For this release I'd like to try tracking known-issues on >>> the wiki page: http://wiki.qemu.org/Planning/2.5 >>> with a list of patch series or bugs which need to be fixed >>> into the release. This will hopefully avoid the problem we >>> had last time around where I missed patches that should have >>> gone into an rc. >> >> Can patches fix this with the right form of query? Maybe another piece >> of metadata for patches that are promoted for rc merge. > > ...only if the submitter remembers to tag it when they send > it, and it doesn't help for issues that don't have a patch yet, > or for tracking whether a submaintainer has taken the patch. > > Tagging your patch as "[PATCH for-2.5]" is a good idea anyway > once we're in freeze, though.
Maybe we also need a [PING for-2.5] or similar? I've just sent another couple of pings for patches (one of which fixes the broken analyze-migration.py script) which have fallen through the cracks over the past couple of months. It would be nice to have an easy way to flag outstanding patches like this, especially during freeze when things get really busy. ATB, Mark.
