While the retag was thorough and may be justified*, it creates a problem. Every other versioned JBoss tag has been left alone, including:
- jboss-3.x, 2 questions
- jboss-4.0.x, 14 questions
- jboss-4.2.x, 59 questions
- jboss-4.3.x, 6 questions
- jboss5.x, 416 questions
- jboss6.x, 262 questions
There was already an inconsistency between the wording in the various version-specific tags, but adding another variation doesn't help. Consistency is good.
- If one of the tags is going to be
-as-'d, then the rest should as well.
- The 5.x and 6.x tags should be hyphenated for consistency regardless.
- We can probably merge 4.0.x, 4.2.x and 4.3.x. I'm not sure why there's no 4.1.x.
While this is being thought about, it may be wise to revisit the jboss tag. The product name has always been "JBoss Application Server." Common colloquial use of "JBoss" alone has almost always been in reference to the application server. However, JBoss was a company (now a division of Red Hat) and offered many products. It is possibly inappropriate to continue the use of jboss due to the potential confusion it can create between the multitude of JBoss-related projects. However, I expect that any of these tag renames are going to create needless confusion. Users don't tend to care about product names that include a company name and some entirely uncreative words. See also, Zend vs Zend Framework.
* The retagging seems to have been spawned by a content dispute last month, where he deemed the existing tag to be inaccurate, despite colloquial use and tag wikis disagreeing.