p17.03.03 changes

This is identical to p17.03.02. We had to change the release name to avoid
conflicts with data generated incorrectly by p17.03.02.