On 01/06/2017 04:56 AM, Jean-Marc Lasgouttes wrote: > Le 31/12/2016 à 15:26, Jean-Marc Lasgouttes a écrit : >> Le 31/12/2016 à 15:24, Jean-Marc Lasgouttes a écrit : >>> It is this particular patch. I amended it since the initial July 5 >>> creattion, but apparently git does not update date by default. >> >> To be more precise, this is the commit below, pushed on Dec 19. I have >> prepared a version for stable (for discussion), that I will post later. > > Here is the backport for stable. I did not have to change much for the > backport, which is good in terms of stability. > > I used it for a few days, and it seems to work fine.
We have 14 bugs fixed in 2.2.x; 5 that are fixed in master with 2.2.3 or 2.2.x milestones; and another 7 that are fixed in master but without any milestone. So I was intending, soon, to try to prod for some action on the latter, looking towards a 2.2.3 release maybe around the end of the month. This could be delayed a bit, if need be, and I guess this slowness has been a problem for some people, so it would be good if we could improve the situation for 2.2.3. I guess I'd be inclined to go ahead and commit it, then. Maybe we can just encourage as many people as possible to use the 2.2.x branch (if they're not already using master), so it gets tested. One question: Do you want to leave all the #ifdefs in the 2.2.x code? They seem to me to be less useful here than in master, but maybe they do no harm. But if they are left, we should probably add something to the release notes about what they do and how to enable/disable them. Richard > > Thoughts? > > JMarc > >
