Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be consistent about versioning in ED URLs #2941

Closed
gsnedders opened this issue Jul 20, 2018 · 3 comments
Closed

Be consistent about versioning in ED URLs #2941

gsnedders opened this issue Jul 20, 2018 · 3 comments

Comments

@gsnedders
Copy link
Contributor

See w3c/webref#11 (comment).

By and large, we use unversioned ED URLs for the current work, and versioned for later levels. We have so few RECs that we don't really have much to go by for earlier levels.

From a quick look, the specs with versioned ED URLs are:

css-animations-2/Overview.bs:ED: https://drafts.csswg.org/css-animations-2/
css-backgrounds-4/Overview.bs:ED: https://drafts.csswg.org/css-backgrounds-4/
css-cascade-3/Overview.bs:ED: https://drafts.csswg.org/css-cascade-3/
css-conditional-3/Overview.bs:ED: https://drafts.csswg.org/css3-conditional/
css-fonts-4/Overview.bs:ED: https://drafts.csswg.org/css-fonts-4/
css-gcpm-4/Overview.bs:ED: https://drafts.csswg.org/css-gcpm-4/
css-grid-2/Overview.bs:ED: https://drafts.csswg.org/css-grid-2/
css-images-3/Overview.bs:ED: https://drafts.csswg.org/css-images-3/
css-images-4/Overview.bs:ED: https://drafts.csswg.org/css-images-4/
css-lists-3/Overview.bs:ED: https://drafts.csswg.org/css-lists-3/
css-multicol-2/Overview.bs:ED: https://drafts.csswg.org/css-multicol-2/
css-overflow-3/Overview.bs:ED: https://drafts.csswg.org/css-overflow-3/
css-overflow-4/Overview.bs:ED: https://drafts.csswg.org/css-overflow-4/
css-pseudo-4/Overview.bs:ED: https://drafts.csswg.org/css-pseudo-4/
css-ruby-1/Overview.bs:ED: https://drafts.csswg.org/css-ruby-1/
css-scroll-snap-1/Overview.bs:ED: https://drafts.csswg.org/css-scroll-snap-1/
css-shapes-2/Overview.bs:ED: https://drafts.csswg.org/css-shapes-2/
css-sizing-3/Overview.bs:ED: https://drafts.csswg.org/css-sizing-3/
css-tables-3/Overview.bs:ED: https://drafts.csswg.org/css-tables-3/
css-text-3/Overview.bs:ED: https://drafts.csswg.org/css-text-3/
css-text-4/Overview.bs:ED: https://drafts.csswg.org/css-text-4/
css-text-decor-3/Overview.bs:ED: https://drafts.csswg.org/css-text-decor-3/
css-text-decor-4/Overview.bs:ED: https://drafts.csswg.org/css-text-decor-4/
css-transforms-2/Overview.bs:ED: https://drafts.csswg.org/css-transforms-2/
css-transitions-2/Overview.bs:ED: https://drafts.csswg.org/css-transitions-2/
css-ui-4/Overview.bs:ED: https://drafts.csswg.org/css-ui-4/
css-values-3/Overview.bs:ED: https://drafts.csswg.org/css-values-3/
css-writing-modes-3/Overview.bs:ED: https://drafts.csswg.org/css-writing-modes-3/
css-writing-modes-4/Overview.bs:ED: https://drafts.csswg.org/css-writing-modes-4/
mediaqueries-4/Overview.bs:ED: https://drafts.csswg.org/mediaqueries-4/
mediaqueries-5/Overview.bs:ED: https://drafts.csswg.org/mediaqueries-5/
web-animations-1/Overview.bs:ED: https://drafts.csswg.org/web-animations-1/
web-animations-2/Overview.bs:ED: https://drafts.csswg.org/web-animations-2/

Needlessly versioned:

  • css-conditional-3/Overview.bs
  • css-images-3/Overview.bs
  • css-lists-3/Overview.bs
  • css-overflow-3/Overview.bs
  • css-pseudo-4/Overview.bs
  • css-ruby-1/Overview.bs
  • css-scroll-snap-1/Overview.bs
  • css-sizing-3/Overview.bs
  • css-tables-3/Overview.bs
  • css-text-3/Overview.bs
  • css-text-decor-3/Overview.bs
  • css-ui-4/Overview.bs
  • css-writing-modes-4/Overview.bs

Other wrongness:

  • css-sizing-4/Overview.bs should be css-sizing-4 (current work is 3)
  • css-ui-3/Overview.bs maybe should be css-ui-3 (current work is 4… do we want to keep the ED pointing at it on the post-REC ED of 3?)
@svgeesus
Copy link
Contributor

svgeesus commented Aug 8, 2018

This is the list of versioning conventions that Webmaster is using for versioning
https://github.com/w3c/tr-pages/wiki/Latest-versions-proposal-for-leveled-specifications

Note in particular the rules for /TR/shortname/latest/

@css-meeting-bot
Copy link
Member

The Working Group just discussed Be consistent about versioning in ED URLs, and agreed to the following:

  • RESOLVED: use versioned URLs for EDs
The full IRC log of that discussion <dael> Topic: Be consistent about versioning in ED URLs
<dael> github: https://github.com//issues/2941
<dael> gsnedders: This is about consistency on using level for ED.
<dael> dbaron: Is this about what the latestest version points to or what's in repo or...?
<dael> gsnedders: I think this is what hte latest version in the draft is linked to. The ED link in TR specs. I could be wrong. I'm not sure, I can't remember
<dael> Rossen_: chris anything to add?
<dael> chris: It wasn't quite the same thing. There's rules for latest version, but doesn't cover ED
<dael> dbaron: I think underlying problem is that CSS conditional hasn't been published since great renaming. I think solution is repub
<dael> gsnedders: Underlying issue is to have a versionless string in TR data which is API exposed. That's not a CSSWG thing
<dael> fantasai: If this is all pulling from a draft we should prob decide if we want versioned URLs for ED links
<dael> gsnedders: Yes
<dael> dbaron: I think versionless is problematic when we have 2 levels being worked on which happens a decent amount of time
<chris> most of the time, I would say
<dael> fantasai: Go with versioned URLs. It's simpler and always correct.
<dael> gsnedders: If use versioned do we want anything linked to a later level. Once we publish as CR and start new work on a new level do we want to link to that level?
<dael> fantasai: That's what TR latest is supposed to be for
<dael> gsnedders: Do we want to link to a newer ED
<dael> fantasai: I think no. Let's say grid 1 and 2 are pub. Having ED link for grid 1 go to grid 2 isn't helpful. If you find issues on L1 you should file them on L1. But if you'relooking for latest you should go to L2. The ED URL shouldn't try to negotiate which level you're looking at.
<dael> gsnedders: Also presupposes we pub a FPWD soon after starting a new level
<dael> fantasai: We do that frequently. When we don't it's because it's really shaky and you shouldn't be referencing it
<dael> Rossen_: To avoid the discussion going into publishing management. URLs and URL versioning. Last proposal that resonated was to stick with using versioned URL. Can we resolve on that?
<dael> Rossen_: Objections to use versioned URLs for EDs
<dael> RESOLVED: use versioned URLs for EDs
<dael> gsnedders: I don't object, but I want to check if there are things we haven't published but we should have

@svgeesus
Copy link
Contributor

We seem to be consistently using versioned ED urls now, 6 years on; and any cases where that is not true, would be better as a separate issue on that one specification rather than one mega-issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants