[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 DrewAPicture):

 Replying to [comment:5 GaryJ]:
 > Is trunk going to be parsed nightly and added to DevHub? For whose
 benefit?
 > Adding documentation to DevHub that's going to be cached by users and
 search engines, but then potentially be out of date the next day anyway
 seems odd.

 Are you under the impression that massive amounts of docs will be changing
 day-to-day? Because I don't see it. I can see doc updates happening
 periodically, yes, but not to the point where it would be causing a
 caching race condition as it were.

 > With everyone being encouraged to always run the latest version of WP,
 and trunk users competent enough to know where to look anyway, I'm not
 sure what the benefit there is for having docs for anything other than the
 latest '''stable''' version.

 I don't see much benefit in parsing docs for anything older than the
 latest "stable" version, and really would rather we only parse !WordPress
 as closely to "now" as possible, e.g. trunk.

 We dearly need to move away from this idea that documentation should
 follow release cycles, and instead embrace incremental change. Without it,
 we're still stuck in the stale documentation rut we're in now.

 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.

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