P4DTI issue job000296

TitleRelease build procedure can generate incorrect list of fixed issues
Assigned userRichard Brooksby
DescriptionThe release build procedure instructs the developer to generate the list of issues fixed in a release using the known_issues.py script, but the logic of the script is incorrect, for example it won't work for finding the jobs fixed in release 1.1.0.
AnalysisWe merged changes from the integration-kit branch to the masters. The changelists for these are interleaved with those for various releases. They include fixes for some jobs, which should count as being fixed in release 1.1.0. But they are excluded because they are before the changelist of the previous release. RB 2001-03-20
It may be that we want all the issues ever fixed minus all the issues ever fixed in the previous release, rather than filtering by changelist, which will only work for linear sources. RB 2001-03-20
Fixed by changing the procedure to use the 'fixed_at_changelevel' query in the issue CGI script. The known_issue.py script is still buggy, but since it isn't used any more it can be deleted. GDR 2001-05-04
How foundinspection
EvidenceOriginal e-mail noting the problem <http://info.ravenbrook.com/mail/2001/03/29/15-06-05/0.txt>.
More notes <http://info.ravenbrook.com/mail/2001/03/30/12-40-51/0.txt>.
Observed in1.1.0
Introduced in1.0.0
Created byRichard Brooksby
Created on2001-04-11 13:22:44
Last modified byGareth Rees
Last modified on2001-12-10 19:38:47
History2001-04-11 RB Created.
2001-05-04 GDR Explained fix.


Change Effect Date User Description
12386 closed 2001-05-04 16:20:17 Gareth Rees Use the issue CGI script to get a list of issues newly fixed in the release.
11321 open 2001-04-11 13:27:17 Richard Brooksby Added warning about known_issues.py script generating wrong results between version branches.