[wp-meta] [Making WordPress.org] #7101: Forged release dates to be reverted to initial

[Making WordPress.org]

#7101: Forged release dates to be reverted to initial
--------------------------------+---------------------
 Reporter:  anrghg              |       Owner:  (none)
     Type:  defect (bug)        |      Status:  closed
 Priority:  normal              |   Milestone:
Component:  WordPress.org Site  |  Resolution:  fixed
 Keywords:                      |
--------------------------------+---------------------
Changes (by dd32):

 * priority:  highest omg bbq => normal
 * status:  new => closed
 * resolution:   => fixed


Comment:

 These are human written pages, this isn't a case of 'forgery' rather human
 error.

 > https://wordpress.org/documentation/wordpress-version/version-6-1/
 Page created on 17th April 2023 with the correct date, Mistakenly updated
 to 2023 on 17th May.

 > https://wordpress.org/documentation/wordpress-version/version-6-1-1/
 Page created on 17th May 2023 with the incorrect date.

 > https://wordpress.org/documentation/wordpress-version/version-6-1-2/
 Page created on 16th May 2023 with the correct date, Mistakenly updated to
 2023 on 17th May.

 I've updated all with the correct 2022 date.

 It looks like these pages were created late, so didn't exist at release
 time.

 It appears that the cause was that a bunch of older point releases were
 created, such as `5.3.15` https://wordpress.org/documentation/wordpress-
 version/version-5-3-15/ with `2022` as the year, where it should've been
 2023. While updating those to the correct 2023 release date the 6.x.x
 pages were incorrectly included in the set of posts that were updated.

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