Template talk:Infobox OS

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Software / Computing  (Rated Template-class)
WikiProject icon This template is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 Template  This template does not require a rating on the project's quality scale.
Taskforce icon
This template is supported by WikiProject Computing.

support status -> release status[edit]

Should support status be renamed to release status? Is that about whether the OS is in alpha or beta stage? See this discussion why I ask: https://en.wikipedia.org/wiki/Talk:Android_N#Release_status   Daniel.Cardenas (talk) 20:59, 15 June 2016 (UTC)

@User:Daniel.Cardenas: Definitely not. Support status is about the support policy of the developer, i.e. for how many years are there technical support, patches, and feature packs. (Canonical and Microsoft both have such policies for Ubuntu and Windows.) Things like alpha and beta stage are handled by |preview version= and |preview date=. Fleet Command (talk) 08:38, 16 June 2016 (UTC)
Need something that indicates the quality of the release. latest preview version looks like it is asking for a version identifier. For android all of the releases are called preview 1, preview 2, etc... But quality is given on this page: https://developer.android.com/preview/overview.html , search for alpha and beta. Should we add a field like quality status that explicitly calls out the quality? Thanks for the help, Daniel.Cardenas (talk) 11:00, 16 June 2016 (UTC)

Displaying more than one stable or preview release?[edit]

Sometimes there might be more than one preview release; for example, iOS and OS X have betas of updates to the current stable release and two betas of the next major release, one for developers and one for users (the two betas for iOS 10 have the same build number, but the two betas for macOS Sierra don't).

There might also be multiple stable releases, although that seems less likely.

The only ways I've seen to display that are:

  • put the full release information - version and release date - in the "latest xxx version" parameter, with a <br/> between them to put them on separate lines, and don't use "latest XXX date" at all;
  • use a template for that information, and use multiple {{LPR}} or {{LSR}} templates in the body of that template.

The former means you don't need a possibly-otherwise-unnecessary template for the release information; the latter means you aren't stuffing dates into "latest xxx version", in case some software cares about the metadata and wants the version and date information separate.

Which of those is best, for articles that don't already have version information templates for other reasons? Guy Harris (talk) 02:25, 8 July 2016 (UTC)

Hey. I don't think you should list multiple version numbers. Only the latest version. The connotation of announcing the next major version is far different from announcing the next major patch, and I think it is quite clear that for Wikipedia infoboxes, which are subject in glance, the former is more important. Fleet Command (talk) 07:03, 8 July 2016 (UTC)
OK, you're saying that the only "preview versions" we should list in any infobox are "next major release" preview versions, not "next software update" preview versions? Guy Harris (talk) 18:19, 8 July 2016 (UTC)
And if an OS has separate developer and public beta versions, as macOS and iOS do, should only the most recent of them be shown (even if, as appears to be the case based on build numbers, a developer beta coming out on July 5 is a newer build than a public beta coming out two days later)? Guy Harris (talk) 21:14, 8 July 2016 (UTC)
I never said only. If someone reported something minor, the best thing is to do nothing about it. (Assuming there is nothing else wrong with the whole contribution.) But I think we should report the latest version (as opposed to the most recent one). When you have a dilemma, answer this question: Which of these versions represent the highest point of the OS development? For example, report XXX v21.0 released 20 July 2015 (latest) instead of XXX v20.203 released 20 January 2016 (most recent). FleetCommand (Speak your mind!) 16:59, 9 July 2016 (UTC)
"I never said only." What you said was "Hey. I don't think you should list multiple version numbers. Only the latest version.", so you did, in fact, say "only".
Your comment pretty much amounts to "don't list betas of updates to the current major version". Others who have updated the infoboxes seem to disagree, so I don't see a consensus either way. Guy Harris (talk) 18:55, 9 July 2016 (UTC)
Don't put words in my mouth. Articles about individual versions of an OS, e.g. Windows XP can still list beta service packs. Windows 10 and Windows 10 Mobile notably update the version numbers often.
iOS and OS X are not the only OS articles on Wikipedia. And it seems so self-contradictory that a field reads "latest preview version" and lists a far-from-latest version. FleetCommand (Speak your mind!) 23:04, 10 July 2016 (UTC)
Not listing, in the main article for an OS, preview versions of updates to the current major release seems reasonable. I'd still want to hear others weigh in on this, however.
That still doesn't address OSes that have, for the next major release, two streams of preview updates, a "developer" stream, and a "user" stream, with the first one presumably intended for people testing 1) whether their existing versions of their software works on new releases and 2) whether under-development versions of their software that uses the shiny new features of the new release works correctly, and with the second one intended for people who want to test 1) whether the new version works for them and 2) whether the shiny new features of the new release work for them. The "developer" stream releases may have a newer build as the latest version than the "user" release does - the expectation might be that people wouldn't use the "developer" releases for day-to-day work but that people willing to live on the bleeding edge might use the "user" releases for day-to-day work - and might even have a newer build come out in the "developer" stream before an older build comes out in the "user" stream.
There might be some who would argue that this means the most recent builds on both streams should be shown. Guy Harris (talk) 00:29, 11 July 2016 (UTC)
The situation you are describing reminds me of Windows 10 that has three release rings: Fast, slow, release preview ring. If you want to ask others, then, according to X!, you should probably ask ViperSnake151, Codename Lisa, NeoGeneric, The Professor123 and Comp.arch. Of course, you can look up OS X and iOS stats but you yourself are the top editor there. (Now that I come to think of it, I have only seen you adding multiple version numbers; it was some office software article.) FleetCommand (Speak your mind!) 07:26, 11 July 2016 (UTC)
If by " I have only seen you adding multiple version numbers" you mean that I'm the only person you've seen adding multiple version numbers, rather than that you've never seen me, for example, reducing multiple version numbers to single version numbers, I'm not the only person who's put multiple versions into inboxes in OS X and iOS articles - I'm not even the person who started the tradition; see, for example, this edit, which put in both software-update and next-release betas, and this edit, which adds separate developer-track and user-track (public) betas.
I'd rather just throw something out to the general public, so I'll try putting something in the talk pages for various OS X, iOS, and Windows pages; if that doesn't provoke any response, I'll consider asking the people you mention, as well as IAdam1n and possibly Bbb2007. Guy Harris (talk) 08:00, 11 July 2016 (UTC)
──────────────────────────────────────────────────────────────────────────────────────────────────── Good idea. FleetCommand (Speak your mind!) 08:11, 11 July 2016 (UTC)
OK, done. I somewhat arbitrarily chose Talk:OS X, Talk:iOS, Talk:Windows NT, Talk:Ubuntu (operating system), Talk:Red Hat Enterprise Linux, and Talk:Debian for OSes and Talk:macOS Sierra, Talk:iOS 10, and Talk:Windows 10 for OS releases; perhaps other Linux distributions, *BSDs, and commercial UNIXes, and various non-UN*X/non-Windows OSes should be included, along with other Darwin and Windows NT derivatives, and so on. Guy Harris (talk) 08:23, 11 July 2016 (UTC)
Hello, Guy Harris
I saw your messages which you have left everywhere. They say that you are comfortable with whatever outcome. Also, I mulled over your rather aggressive conversation with FC here. The rather contrasting attitudes notwithstanding, please tell me what is the core problem anyway? Is there something you want done and can't?
Best regards,
Codename Lisa (talk) 14:05, 12 July 2016 (UTC)
No, there isn't. All I want is to make sure that all sides are represented in this discussion, and some conclusion reached as to whether this infobox should support showing multiple preview and stable releases. If the conclusion is that it should, it should perhaps be modified in some way to do so more easily; if the conclusion is that it shouldn't, the places where it's showing that should be changed not to do so. Guy Harris (talk) 16:58, 12 July 2016 (UTC)
I am against changing this. Adding different preview versions adds unnecessary detail to the infobox and I do not see why it is not sufficient to mention the most recent version. The iOS 10 infobox is already far too bloated and repeats information that is presented well in the article itself, using lists or tables.–Totie (talk) 15:14, 20 July 2016 (UTC)

Deprecated fields lack a description and emphasis on deprecated status[edit]

I couldn't find a way to change deprecated status value to <strong>, like the way a required value is emphasized. It's also not very appropriate to use the description field of a deprecated field to state the deprecation status again, because that should be reserved for explaining the actual purpose of the feature. There was also a problem with Codename Lisa using uppercase letters to denote deprecation which may break accessibility, but I've fixed this. It would also be nice if the background color of those table rows could be changed for deprecated features, but I have no idea how to do this with templatedata. (talk) 05:09, 7 September 2016 (UTC)