Timeline for Synonomize tags for new Firefox
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2017 at 20:14 | comment | added | fixer1234 | @nemo, one other thought - right now, we're dealing with lots of questions relating to the change in code base that will apply to multiple versions of Firefox, so the best tag would be something that differentiates the code base but isn't version-specific. But we also create version-specific tags when a single version has unique issues that generate a lot of questions. So if V58 is a disaster, we could create a version-specific tag for it, and that wouldn't change usage of a "57+" tag for issues relating to the V57 code base change. | |
| Nov 25, 2017 at 19:52 | comment | added | fixer1234 | @Nemo, my assumption is that people would understand "57+" to mean V57 or later, so we wouldn't need to change or replace the tag (unless Mozilla eventually comes out with another new code base with a new set of issues). Your point was my concern with using "57" to also refer to later versions. We would clarify usage in the wiki excerpt (for the two users who bother to read the excerpts). :-) | |
| Nov 25, 2017 at 18:53 | comment | added | Nemo | @fixer1234 maybe but would that force us to remove/change the tag again when firefox 58 comes out and some of those questions are found to be superseded? | |
| Nov 25, 2017 at 17:51 | history | edited | fixer1234 | CC BY-SA 3.0 |
suggest 57+
|
| Nov 25, 2017 at 17:47 | comment | added | fixer1234 | @Nemo, maybe we should change the tag to [firefox-57+], which would reflect that better. Normally, version number tags are explicitly about that specific version. That may actually be the most easily understood choice for the primary tag. | |
| Nov 25, 2017 at 10:58 | comment | added | Nemo | I created [firefox-57] for questions which specifically referred to Firefox 57 or 57+ because for now I cannot tell which is which (for instance some extensions which broke in 57 may resume working in 58 when new APIs are released). I agree they may need to be merged in the future if there aren't many questions about version 57 specifically, but I'm not sure we can predict it now. | |
| Nov 24, 2017 at 16:34 | history | tweeted | twitter.com/super_user/status/934097954801094656 | ||
| Nov 24, 2017 at 6:02 | comment | added | user1306322 | Quantum is basically v57+ until some other browser engine refresh occurs and is called something else. I'd expect the questions relevant to this tag to be about the webextensions which don't work on versions <57 and the new UI. Yay to its own tag. | |
| Nov 23, 2017 at 3:47 | comment | added | fixer1234 | @Braiam, I think we're in agreement conceptually. It isn't clear, though, what you recommend specifically to do with the tags. | |
| Nov 23, 2017 at 3:30 | comment | added | Braiam | "because old answers to problems that are similar to new ones may not be relevant" keyword: may not. And evaluating which one is and which is not is a daunty task that no one will sign up for. I prefer keeping separate stuff where I'm sure that backwards and forwards they will never intersect. Parallels tags, so to say. | |
| Nov 22, 2017 at 21:35 | comment | added | fixer1234 | @Braiam, good point. Right now, we're getting a lot of questions specific to the revised code base, so it's useful to have a tag that differentiates the code base. There are also users sticking with the ESR version (old code base). So in a year, the vast majority of users will be on the new code base and that will be what the new questions are about. It will still be important to differentiate, though, because old answers to problems that are similar to new ones may not be relevant. What's your suggestion for what to use as a tag? | |
| Nov 22, 2017 at 21:19 | comment | added | Braiam | Once all supported versions of Firefox are quantum, would any differentiation matters? AFAIK, Firefox has been Firefox since its Phoenix days and has suffered several mayor reworks in both backend and front end. For the future reader, they will not care how it was called then, but now. | |
| Nov 20, 2017 at 8:41 | history | edited | fixer1234 | CC BY-SA 3.0 |
added 370 characters in body
|
| Nov 20, 2017 at 8:36 | history | edited | fixer1234 | CC BY-SA 3.0 |
added 370 characters in body
|
| Nov 20, 2017 at 8:29 | history | asked | fixer1234 | CC BY-SA 3.0 |