[wp-meta] [Making WordPress.org] #331: Code reference requires archive page to display by version

[Making WordPress.org]

#331: Code reference requires archive page to display by version
----------------------+-------------------------------------
  Reporter:  siobhan  |      Owner:  Rarst
      Type:  defect   |     Status:  assigned
  Priority:  normal   |  Component:  developer.wordpress.org
Resolution:           |   Keywords:
----------------------+-------------------------------------

Comment (by GaryJ):

 Replying to [comment:6 DrewAPicture]:

 > Think of it this way: If we only parsed the latest "stable" version,
 outdated/incomplete/inaccurate docs updated today will not be "available"
 until the next version is released. That's crazy.

 That's a fair point, but the converse is also true - if trunk introduces a
 new function, and it's documented, then it will appear on DevHub whenever
 the WP-Parser is next run, regardless of whether the next version is out
 or not.

 To counter-argue my own point, I guess making the `@since` tag clearly
 visible would help mitigate some of the confusion, especially if anything
 with `@since` greater than stable comes with a clear notice that it's
 something from the future.

 In that case, it makes total sense to be *only* be parsing trunk (not even
 stable).

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