{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/tr-design/issues/52","repository_url":"https://api.github.com/repos/w3c/tr-design","labels_url":"https://api.github.com/repos/w3c/tr-design/issues/52/labels{/name}","comments_url":"https://api.github.com/repos/w3c/tr-design/issues/52/comments","events_url":"https://api.github.com/repos/w3c/tr-design/issues/52/events","html_url":"https://github.com/w3c/tr-design/issues/52","id":134475773,"number":52,"title":"Using dated version is not great","user":{"login":"marcoscaceres","id":870154,"avatar_url":"https://avatars.githubusercontent.com/u/870154?v=3","gravatar_id":"","url":"https://api.github.com/users/marcoscaceres","html_url":"https://github.com/marcoscaceres","followers_url":"https://api.github.com/users/marcoscaceres/followers","following_url":"https://api.github.com/users/marcoscaceres/following{/other_user}","gists_url":"https://api.github.com/users/marcoscaceres/gists{/gist_id}","starred_url":"https://api.github.com/users/marcoscaceres/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marcoscaceres/subscriptions","organizations_url":"https://api.github.com/users/marcoscaceres/orgs","repos_url":"https://api.github.com/users/marcoscaceres/repos","events_url":"https://api.github.com/users/marcoscaceres/events{/privacy}","received_events_url":"https://api.github.com/users/marcoscaceres/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-02-18T04:01:07Z","updated_at":"2016-02-26T03:46:30Z","closed_at":"2016-02-18T05:22:01Z","body":"Can I kindly ask that we refrain from using a year (e.g., \"2016\") for the directory that holds the redesigns? Using years is known to be problematic (the W3C in particular should know this, as it has a long legacy of using dated URLs poorly). Instead, please tag versions using git and please just use two directories: \r\n\r\nThat is, if a resource is stable:\r\nhttps://www.w3.org/StyleSheets/TR/\r\n\r\nOtherwise, it's experimental and should go here: \r\nhttps://www.w3.org/StyleSheets/TR/experimental/\r\n\r\nHaving dated versions makes a huge mess for tools like ReSpec because it means we need to unnecessarily maintain a list of all the possible different experimental versions year over year. Which is a maintenance burden. \r\n\r\nIf a user wants to opt into \"experimental\", then they can just set a flag in ReSpec's conf. However, right now, we are having to special case an `useExperimentalStyles` options using either a boolean or a year. \r\n\r\nIf we keep using a year, we are going to make \"useExperimentalStyles\" just default to \r\n`new Date().getFullYear()` and hope for the best ... which would be sad. \r\n"},"comment":{"url":"https://api.github.com/repos/w3c/tr-design/issues/comments/189099322","html_url":"https://github.com/w3c/tr-design/issues/52#issuecomment-189099322","issue_url":"https://api.github.com/repos/w3c/tr-design/issues/52","id":189099322,"user":{"login":"tripu","id":1016538,"avatar_url":"https://avatars.githubusercontent.com/u/1016538?v=3","gravatar_id":"","url":"https://api.github.com/users/tripu","html_url":"https://github.com/tripu","followers_url":"https://api.github.com/users/tripu/followers","following_url":"https://api.github.com/users/tripu/following{/other_user}","gists_url":"https://api.github.com/users/tripu/gists{/gist_id}","starred_url":"https://api.github.com/users/tripu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tripu/subscriptions","organizations_url":"https://api.github.com/users/tripu/orgs","repos_url":"https://api.github.com/users/tripu/repos","events_url":"https://api.github.com/users/tripu/events{/privacy}","received_events_url":"https://api.github.com/users/tripu/received_events","type":"User","site_admin":false},"created_at":"2016-02-26T03:46:30Z","updated_at":"2016-02-26T03:46:30Z","body":"> Ok, can we please then assure that dirs 2017, 2018, etc. become available year over year. This will allow ReSpec to opt into \"latest experimental\" without needing to specify a particular style year. I'll support explicitly opting into a year also in ReSpec, but will default to `new Date().getFullYear()`.\r\n\r\nAutomatically associating `useExperimentalStyles` to the *next* year (right?) in ReSpec sounds good to me, @marcoscaceres. The caveat is that the cutoff date from year to year will vary (see our two consecutive delays this year). This year, for example, starting 1 January one would assume that `useExperimentalStyles` should point to the 2017 version (the next one being developed). But today `useExperimentalStyles` still means `2016`, since we haven't rolled out the update yet&hellip;"}}