Re: Issues marked as fixed in 25.2

[John Wiegley]

>>>>> "GM" == Glenn Morris <address@hidden> writes:

GM> I suggest looking at the date the issue was closed and comparing it to the
GM> date the version numbering was changed. But then you also need to check
GM> for issues that have been backported since. And you might also want to
GM> review every such issue to see if it _should_ be backported now.

Btw, it's exactly this sort of confusion that I wanted to avoid by using a
3-branch scheme (current release target, next minor, next major).

The 2-branch scheme we have now makes this sort of confusion a regular part of
ongoing development, because we'll always encounter the case where a fix on
'master' ends up becoming part of the next release, ahead of whichever version
master was marked as at the time the bug was fixed.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2