On Mon, Oct 26, 2015 at 2:27 AM, Peter Maydell <peter.mayd...@linaro.org> 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,
If it is done as an annotation (e.g. like an RB) then it can be done by reviewers after the fact. and it doesn't help for issues that don't have a patch yet, > or for tracking whether a submaintainer has taken the patch. > Don't those issue exist regardless of freeze state? We should come up with a more universal state tracking solution. FWIW, In my own local system I use Applied-by: tags so I know something is sitting in someones queue waiting for a flush. Regards, Peter > Tagging your patch as "[PATCH for-2.5]" is a good idea anyway > once we're in freeze, though. > > thanks > -- PMM
