[wp-meta] [Making WordPress.org] #4298: Inaccurate dates in release archive

Making WordPress.org noreply at wordpress.org
Wed Nov 13 21:19:12 UTC 2024


#4298: Inaccurate dates in release archive
----------------------------+-----------------------------
 Reporter:  SergeyBiryukov  |       Owner:  SergeyBiryukov
     Type:  task (blessed)  |      Status:  assigned
 Priority:  lowest          |   Milestone:
Component:  General         |  Resolution:
 Keywords:  needs-docs      |
----------------------------+-----------------------------

Comment (by eidolonnight):

 Replying to [comment:5 dd32]:
 > Assuming the dates of the parent folder in the ZIP/Tars are correct
 (usually `wordpress/` but sometimes `wordpress-.../`), this seems to get
 the right list of dates:
 > If anyone can confirm those dates, I'll see if Systems can update it.
 > These are stored with a SVN repo, so the dates might actually be tied to
 the commit timestamp instead, in which case we may just need to hard-code
 some of these dates.

 In all verifiable cases, these dates match those found in
 https://wordpress.org/news/. Exceptions are:
 - Releases like 1.5.1.3, which was modified after the post date assumably
 for security reasons.
 - A few announcement posts came just a day later.
 - Not all Beta and RC releases were announced on WordPress News.

 Considering the suspicion that would be raised downloading a release and
 seeing files with a different modification date, @ryelle and I agree that
 we should use the Zip dates listed here as canonical.

 @dd32 you can move ahead with the Systems request. @ryelle also offered to
 hardcode the dates if necessary.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4298#comment:15>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list