Improve latest version headers

[plehegar]

since respec doesn't support more advanced handling of latest versions, here is an extension in the meantime. If we like it, we should adopt it across all webperf docs.

[igrigorik]

Preview: https://cdn.rawgit.com/w3c/hr-time/a84265ab296a36882d82be486eb74f7c36dfa63d/index.html

@plehegar what about "latest version" -> "latest stable version"? I find "this version" vs "latest version" a tad confusing.. Implying that "this version" is not latest, but latest actually points to L2?

[plehegar]

I hesitated on that one. I started by writing down stable then backed away because "stable" could means different things depending on who one talks to. Today, we probably consider hr-time-2 to be stable but we'd want hr-time to point to hr-time-3. correct?

[igrigorik]

Fair enough. I guess I don't have a good suggestion here.. I will say, I do find these links really confusing across all of the W3C docs -- I never know which one to click on. But, perhaps that's just me :-)

[plehegar]

That's not just you and i started an effort to fix that within 6 months.

[plehegar]

I'll give more thoughts on this one. Let's not merge this until we feel comfortable or we think it's at least a bit better than what we have.

[igrigorik]

@plehegar any updates on this one?

[plehegar]

Let's hold on this one until the end of May: https://lists.w3.org/Archives/Public/spec-prod/2017JanMar/0014.html

[igrigorik]

@plehegar any resolutions from discussions in May?

[igrigorik]

@plehegar closing, we can reopen if/when needed.