[wp-meta] [Making WordPress.org] #5412: Add offers for 'release-candidate' and 'beta' to Core API version check

[Making WordPress.org]

#5412: Add offers for 'release-candidate' and 'beta' to Core API version check
-------------------------+---------------------
 Reporter:  afragen      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by afragen):

 I think we're on the same page re: updating the API response AFTER the
 beta or RC release.

 I envision something like adding a query arg as follows.

 `beta-RC` returns a download package with the highest release of a beta or
 the highest release of release candidate if that is available.

 `release-candidate` returns a download package with the highest release of
 a release candidate if that is available.

 When the next stable release happens the download package should return
 that. As the user would still be on a ''development'' branch when the next
 beta or RC happens after a stable release the user would then ''see'' an
 update to that next releases beta or RC.

 If the user is not on a development release or the specific query arg is
 not present nothing changes.

 Does that make sense?

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