product release finder set all release dates to the date the file was found

[Stuart Bishop]

The product release finder set all the release dates to CURRENT_TIMESTAMP. We should write a single use script to examine the archives we downloaded, extracting the most recent timestamp from the stored files and updating the release date of the ProductRelease.

[James Henstridge (jamesh)]

The ProductRelease table has a "datecreated" column. The plan discussed in bug 4557 was to add a second "releasedate" column that could be NULL and is user editable.

So this bug would be about filling in the dates based on the downloaded tarballs.

[Curtis Hovey (sinzui)]

This was fixed in March 2009.

[Michael Kuhn (suraia)]

Are you sure? The product release finder still sets "datereleased = datetime.now(pytz.UTC)".
All my recent releases were imported with the current timestamp instead of the release timestamp (extracted from the tarball, Last-Modified header, or whatever).

[Edwin Grubbs (edwin-grubbs)]

I'm not sure why I had re-opened this. This was fixed in March 2009.

[Christian Reis (kiko)]

Sorry for preemptively reopening this, but I believe that https://edge.launchpad.net/linux/+series shows that this bug isn't quite fixed -- or at least the symptom has reappeared for some unrelated reason. If you look at the releases that PRF created across all those series, they all have the date of the PRF run that created them, and not the dates of the release tarballs it found. Ironically the dates of the actual tarballs are correct, since if you look at https://edge.launchpad.net/linux/ you'll see that the date of 2.6.31.tar.gz is correctly set to 2009-10-10.