11

I just noticed, that the tags for questions, regarding a specific OS version are not named consistently. We have 1, , and . For Windows Phone 8 we have and

I think a pure number like 7.0, 7.5 and 7.8 should be preferred. It should be clear, that we are talking about windows phone. Since I do not have enought reputation to suggest tag synonyms nor create tags and I did not found a question here on meta regarding this topic, I want to discuss this with you.

Reform the tags

Here are my suggestions:

  • All questions regarding a specific OS should go to and
  • Questions regarding a specific update should go to , , ...

And for the existing tags, I think, some should be renamed:

1Note
2Questions regarding the update progress in general should go to .

Windows Phone version numbers

There has been some confusion about versions in the comments an the answers. This should only be a little note on version numbers for Windows Phone, leading me towards the previously described proposal:

Actually there are three ways to describe a version:

  1. The "official" or "end-user" version number (e.g. 7.5, 7.8)
  2. The codename (mango, tango, apollo, NoDo, ...)
  3. The "internal" version number (e.g. 7.10.8862.144 for WP 7.8 - note that the internal number actually starts with 7.10!)

I think, we should only focus on the first two points, because they are what's actually provided to the end-user. The update 7.8 actually consists out of multiple updates (at least 3 for me) and one bug fix. The latest version is 7.10.8862.144 and is the only one provided in the version history below. Mango or 7.5 also required multiple updates. However there's allways a change in the minor version number. I think this is what we should focus on. The codenames as tag synonyms and the official version number as usual tags.

Official sources:

  • Agreed. But how about an specific version, like Portico? Maybe we can use the OS version and a tag with this name too, separately. – Vitor Canova May 17 '13 at 10:39
  • I would not tag them seperately. What's the advantage, of (e.g.) tagging a question as 7.5 AND mango? I'd rather suggest using codenames as tag synonyms... ;) – Aschratt May 17 '13 at 11:20
  • 1
    Also, what's Portico? The code name for the versions isn't that well known outside of development circles - I'd go along with the proposal, and suggest it should be the pure version number in the "Software" line of the about line (e.g. 7.8; not 7.10.8862.144) – Rowland Shaw May 17 '13 at 13:29
  • I totally agree with @RowlandShaw. If we really want/need codename-tags, then I suggest creating them as tag syonyms. – Aschratt May 17 '13 at 14:35
  • @Aschratt I can see a problem with calling WP Mango and Tango as 7.5. We need this information sometimes. Like Nokia Counter., it only run in Tango and above, as far as I know. And Rowland, actually many non dev people call this by its codename. In fact I really don't know the exact version number of Mango, Tango, Portico and so on. But I understood you point. – Vitor Canova May 17 '13 at 15:14
  • One other thing, I'd consider [7.x] as for any version of 7, but not 8; with this in mind, should wp8/8.0-apollo become [8.x], rather than duplicate the windows-phone portion? – Rowland Shaw May 17 '13 at 15:18
  • 3
    @VitorCanova I'd prefer to be inclusive with our audience. My wife has a Windows Phone, and she would have no idea if it is running mango/tango/jellybean/portico/collonade/apollo/daphne. She does know that she is running 7.5, and is waiting to update to 7.8 though. – Rowland Shaw May 17 '13 at 15:24
  • @VitorCanova I think Tango is probably a special case that can be ignored. Time will tell of course if a similar release happens, but I don't think Tango deserves its own tag. – row1 May 18 '13 at 3:13
  • I liked the [7.x] idea. I think I'm not so "open minded" right now. You are all right about that people don't know about name version. ;) – Vitor Canova May 18 '13 at 13:14
  • Due the confusion with version numbers I've updated the question. – Aschratt May 21 '13 at 10:05
6

I suggest we drop the code names from all of the tags. Now that time has passed since their common usage, it looks incorrect to see 8.0apollo or 7.5mango. It is clear enough to mention just the number or wp8.

I actually prefer the wpX.X syntax as most enthusiast podasts use that format as well.

ADDITIONALLY: Since this post has started there has not been a real need to create GDR1, GDR2 or GDR3 tags for the additional functionality that these updates give to WP8. It seems ridiculous to keep the codenames on the tags.

5

I suggest looking at Android Stack Exchange:

They seem to use the following format:

  • Tag Name: TwoDigitVersion-CodeName
  • Synonyms: TwoDigitVersion, CodeName, OS-TwoDigitVersion

Example:

  • Tag Name: 4.1-jelly-bean
  • Synonyms: 4.1, jelly-bean, android-4.1

They do not seem have have a catch all tag for the OS major version e.g. there is no '4' or 'android-4' tag. So I would suggest that and are overkill and not needed. There is no harm in tagging a generic Windows Phone 7 question as .

A difference is that for Android the code name is also a marketing name, whereas (as far as I can see) Microsoft seems to drop the code name once released, so as per the comments, a lot of people don't know the code names.

If you look on Super User, they do not include the code names at all in their Windows Tags:

So, I would actually suggest removing the code names all together. The code name doesn't actually provide any useful information, Microsoft isn't using it, and if people know the code name then they know the actual two-digit version number. Perhaps Tango is a special case as it was 7.5, but really Tango was a very minor and short lived update, its new features were better supported by a separate tag .

So I would suggest the following

  • Tag Name*: Two-digit OS version e.g.
  • Synonyms*: OS-TwoDigitVersion e.g. tags in this format seem to be banned
  • Delete/Rename the code name tags e.g. and
  • Remove the OS catch all tag e.g. and [wp8].

*perhaps these two could be swapped—as I new user I would probably first try to tag it as .

  • I also don't think we actually need the codenames. That's why I would suggest them as synonyms. I've also updated the question. – Aschratt May 21 '13 at 10:08
  • 2
    Even as a synonym I am not sure that they are actually needed. To me, Windows Phone code names are the names for the pre-release version, the code name doesn't actually get released or marketed to the user, so following the example by Super User of not using them for Windows tags makes sense. – row1 May 22 '13 at 5:34
  • What about in the case of Lumia Black, which included WP8 Update 3 along with Nokia specific updates? – Cindy Jayakumar Jan 31 '14 at 5:20
  • @Arabella Lumia Black is a shipping name for a convrete set of features. You need to remember that Lumia Black's codename was Bittersweet Shimmer (orange). It makes sense to have tags for the common shipping names of a product, like black, but not to the codenames, which become irrelevant with time. Shipping names like Lumia Black can always be referenced to mean the same thing. Codenames can be reused (especially at Microsoft). – caschw Feb 9 '14 at 5:04
  • @caschw I see your point. It would stand to reason that the codenames be used before the product is released because genuine questions may come up during the testing period, but then to do a clean up after release to ensure the questions are tagged with the release name. Sounds like a lot of work though. – Cindy Jayakumar Feb 10 '14 at 5:43
  • 1
    @Arabella I don't think we need to tag rumors or pre-release codenames – caschw Feb 10 '14 at 14:09
2

Actually we do need the codenames, but as probably as separate tags. For example MS is now making Windows Phone Blue available for testing to selected users. We still don't know if it's going to be Windows Phone 8.1 or if they are going to create some other name.

The system needs to be flexible enough so it can accompany Microsoft's name changes and schemes. Things are going to change as Microsoft will combine Windows Phone and Big Windows (RT/Pr) resources and dev teams.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .