I started this question thinking specifically about the Jelly Bean synonym issue, as exposed below, but then I realized that it can probably be generalized.

I think we should always synonymize versions to code names and not the other way around. While it can happen for different versions to share the same code name, the opposite seems quite unlikely.

Another approach could be to use both version numbers and code names in the tag name, as suggested by Al Everett in the comments. This has been done in Android Enthusiast, where for instance Android 4.3 questions are tagged [4.3-jelly-bean].

On StackOverflow tags like or would be a good way of tackling this issue, IMO.

Original question

As a follow up to Merge and synonymize Android version tags and https://meta.stackexchange.com/questions/203882/synonym-request-kitkat-android-4-4, we currently have


but Google kindly named Android 4.3 Jelly Bean as well.

Currently has no synonyms, but it has the same exact rights as to be pointed by (and ).

So we have this situation

| ====>
| - - - ->
| - - - -> (hypothetically, since such tag doesn't exist)

Since it makes no sense for a synonym to point to two different tags, how can we handle this?

Should we invert the synonym relationship and have


  • I would prefix the codenames with "android-" though. And in addition, make sure the excerpt tag wiki lists all the applicable android version numbers for easy reference. – Jeff Mercado Nov 2 '13 at 18:14
  • Agreed, I edited my question a bit and I also noticed that [jelly-bean] is synonymized but [jellybean] is not. – Gabriele Petronella Nov 2 '13 at 18:23
  • I'd say these are excellent points not to have jelly-bean or kitkat tags. – Bart Nov 2 '13 at 18:34
  • @Bart not sure. Code names are very common when referring to a version and I wouldn't feel completely ok in eradicating such tags. Also, due to their popularity, removing them would be useless, unless they are blacklisted. And I hardly doubt all code names tags will be considered as good candidates for blacklisting. – Gabriele Petronella Nov 2 '13 at 18:38
  • Then at most I'd keep them completely separate. Because whatever synonymization you'd choose, you would end up with a less than ideal situation. – Bart Nov 2 '13 at 18:39
  • 3
    Over at Android Enthusiasts we've "solved" this issue by using version numbers with codenames, e.g., 4.1-jellybean, 4.2-jellybean, 4.4-kitkat – ale Nov 2 '13 at 18:40
  • Ooh, that's not a bad one @AlEverett. – Bart Nov 2 '13 at 18:41
  • @Bart I don't think keeping them separated would lead to any benefit. For instance, [android-4.4] and [kitkat] clearly refer to the same thing. If they exist they should be synonymized, in one direction or the other, IMO. – Gabriele Petronella Nov 2 '13 at 18:42
  • @AlEverett that's a clever solution. I would like to see it applied on StackOveflow too. – Gabriele Petronella Nov 2 '13 at 18:45
  • 2
    Unforunately, the Android Enthusiasts solution to the problem doesn't (and shouldn't IMHO) apply to Stack Overflow. Android anything is implied there, but not at Stack Overflow. Tagging in that manner would only leave the site littered with very cryptic tag names. Imagine if every set of tags in Stack Overflow did that. It would do more harm I'm afraid. – Jeff Mercado Nov 2 '13 at 19:36
  • 1
    @JeffMercado, I understand the concern, but [android-4.3-jelly-bean] doesn't look cryptic to me. – Gabriele Petronella Nov 2 '13 at 19:37
  • Right, that's a nice compromise. I was more concerned about the introduction of the [4.1-jellybean] tag and friends. – Jeff Mercado Nov 2 '13 at 19:39
  • @JeffMercado I agree. I like the approach, but I never suggested to copy such tags verbatim, as you can see in my question ;) – Gabriele Petronella Nov 2 '13 at 19:43
  • @animuson I've seen your edit. Why [jellybean] shouldn't be synonymzed to [android-jelly-bean]? It's used in the exact same way as [jelly-bean] – Gabriele Petronella Nov 5 '13 at 2:26
  • @GabrielePetronella meta.stackexchange.com/questions/147233/… – animuson Nov 5 '13 at 2:27

This issue has been lingering long enough. I went ahead with the method already utilized on Android Enthusiasts and just appended the codename to each version tag, leaving us with:

Let me know if I missed any. Also, all of the original "android-x.x" tags were synonymized into their respective new tags.

has been destroyed as well.

| improve this answer | |
  • +100 This is definitely the way to go. We didn't really get any information from a generic "jellybean" tag that we didn't already get from a version tag. – Jason C Apr 5 '14 at 18:36

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