[wp-meta] [Making WordPress.org] #5506: Add version validation to Release tooling

Making WordPress.org noreply at wordpress.org
Fri Nov 13 02:48:46 UTC 2020

#5506: Add version validation to Release tooling
 Reporter:  dd32                |      Owner:  (none)
     Type:  defect              |     Status:  new
 Priority:  normal              |  Milestone:
Component:  WordPress.org Site  |   Keywords:
 The WordPress.org release management tooling currently trusts the user
 filling out the forms, and prefills/includes details about what it's going
 to release, but it's easy to forget / miss something.

 For example, today beta4 was originally packaged as `5.6-beta4-49588`
 rather than `5.6-beta4`, a mistake that has happened numerous times before
 (Sometimes due to core.svn builds being delayed, others just mistakenly
 not bumped the right digits).

 In the past we've also had `x.y-Beta1` (should be lowercase, unlike
 `x.y-RC1`) and also minor versions skipped (ie. releasing `x.y.3 -> x.y.5`
 instead of `x.y.4`, unintentionally skipping a digit), both of which
 should easily be prevented with some simple version checking in the UI.

 There's also some checks in place to work with/prevent the re-releasing of
 packages, so more UI around "This doesn't quite look right, are you sure?"
 would benefit others in the future.

 cc @helen and @SergeyBiryukov since you've been doing most releases
 lately, is there anything else that comes to mind that I've missed here?
 If it's something that human eyes can say "That doesn't look quite right"
 then surely some big red text to that effect wouldn't go astray :)

Ticket URL: <https://meta.trac.wordpress.org/ticket/5506>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list