Michael Gerz wrote:
Sorry but I can't fix all open change tracking issues in one week. (I may ask for some assistance after the weekend, when it becomes clear what is missing)
Notice that José is the release manager - not me. I do not get to set the target.
When that is said, and with all due respect, I do not think perfect change tracking should block a test release.
The purpose of the test release is to get the software tested by a wider, willing audience so that the currently UNKNOWN important problems are identified so they can be fixed before a pre-release can be rolled out to an even wider audience.
Having a list of known issues with change tracking (and other things) will not stop that from happening. If the known issues are not show-stoppers, or likely to hide or introduce other problems when they are fixed, I think it's fine just to list them.
Regards, Asger
