Problem/Motivation
We discussed in a migrate meeting the fact that creating and rerolling patches with the test fixtures is time consuming and maybe it would be better to update the fixtures with the data for all remaining issues.
It is common to need to bring up a D6 or D7 site using the fixture database in order to enter data. Then, when that database is dumped using db-tools an incredible number of other changes appear in the fixture. For example, every single row of the system table changes, search creates rows etc. Including that in the patch makes for a large patch which makes it difficult for the reviewers, who expect the patch to include only the relevant changes to the fixture. So, the practice is to edit out the unnecessary changes to the fixture in the patch. Of course, for some small changes when you know where to look it is possible to find and keep those. Often that is not the case.
This has been discussed before in #2670846: Add i18n data to d7_dump. In that issue, comment #15, maxocub makes good points about the value of adding the data per issue.
Proposed resolution
Make a new fixture for D6/D7 that adds the data needed for Active issues. Anything already being worked on continues as is.
Remaining tasks
Investigate what D6 and decide if the fixture should be updated for remaining active issues.
Investigate what D6 and decide if the fixture should be updated for remaining active issues.