0

So the release of Windows 10 on July 29th 2015 was known as Threshold 1. The current release is the Threshold 2 build. It was released on November 12th 2015.

Threshold 2 bring several specific enhancements to Windows 10. Some of those things are not possible in build 10240 (Threshold 1). An example of this would be installing Windows 10 with a Windows 7, Windows 8, or Windows 8.1 license key.

There are some other generic improvements that also come with Threshold 2. In the end there are several major and minor things that make these two builds different enough that warrant separate tags.

I feel this is an important to decide, because when the next update, Windows Anniversary Edition is released Microsoft Edge will support extensions. So any answers to questions about Microsoft Edge today might not apply to a user running Windows 10 Windows Anniversary Edition in a year.

It will be possible to defer Windows Anniversary Edition and Threshold 2 for a period of time on Windows 10 Professional and Windows 10 Enterprise installation. So although these updates are "required" there is still a legitimate need to separate questions even if we are only applying these changes to old questions asked before these updates are released.

So how do we separate Windows 10 questions? This same question can be applied to the next updates Windows Anniversary Edition in 2016. Looking forward the changes between these builds, will be as different as, Windows 8 and Windows 8.1 are to one another.

As somebody who performed the update to Threshold 2 I can say to the end user, it appears that Windows 10 is being installed again, so this is a major update. This isn't as simple as installing a service pack.

So my suggestion would be to rename the current Windows-10 tag to Windows-10-TH1 and update the description. Now that Threshold 2 is officialy released we should create a Windows-10-TH2tag and update the description to indicate the difference between the two releases. I feel this would would be similar to the Office-XXXX tags we have currently.

Below is a screenshot of the next Windows Insider branch (RS1_Release) which is believed to be the Windows Anniversary Edition aka the Redstone branch.

enter image description here

Other Information:

Threshold 2 is known as the Fall Update which will be reported as Windows 10 Version 1511 (for 2015 November) and and likely be the 10586.3 build.

  • 2
    There are some specific questions where the distinction will be important, but I've got to wonder whether tag misuse would be a bigger problem overall. The OP can always specify the version in the question. Too much granularity makes it harder for those people who want to follow subject tags. – fixer1234 Nov 10 '15 at 19:27
  • 2
    That question is a good example. The average user isn't going to know one Threshold from another or build numbers, so usage of the tag is likely to be spotty and unreliable. – fixer1234 Nov 13 '15 at 18:34
  • Maybe the answer is to wait for a sample of questions to come in and judge from that how well the tag is likely to be used. Information-based decision making. :-) – fixer1234 Nov 13 '15 at 19:00
  • Looks like someone already created and started using windows-10-v1511 - and that seems to be the new official versioning scheme from MS. So if we do end up keeping the split tags then that might be better than TH2..? – Bob Nov 17 '15 at 4:35
  • I feel like if the user is knowledgeable enough to know the difference, they'll say it. Else, if they don't know, they'll pick a tag at random either TH1 or 2. 'How do we handle it' to me is by doing nothing but being diligent in asking for build numbers in the comments of questions that are ambiguous. – Insane Nov 18 '15 at 17:20
  • @Ramhound Out of the two, I would certainly prefer the version number - that is what appears in the Version field in system info. Also "Fall Update" doesn't make much sense for those of us in the Southern hemisphere - it's Spring right now! :P – Bob Nov 18 '15 at 19:02
3

Consistency would be that we treat these the same way as we would and and have a new tag for each major(ish) version.

What to name those tags though is the question. and lacks a certain je ne sais quoi as a tag, but as Microsoft isn't naming them something more relevant such as SP1 or 10.1 then it's the best we can really do. If the question is relevant to all versions then the base tag would be preferred.

I had been hoping that these would sound a lot more like real releases than minor feature packs.

  • Users don't even know the difference between if it's a problem of 8.1 or 8, does anyone really expect they would use the correct tag? Or worse, would anyone expect there would be users that will waste their time trying to figure out which tag is appropriated? This only would reduce the visibility of the questions, without any marginal gain. – Braiam Nov 16 '15 at 0:39
  • I explained the benefits did you even read my question? – Ramhound Nov 16 '15 at 1:37
  • 1
    @Ramhound it reads as: I want a new shinny tag. Bring hard data. Its only 2 new questions/day on the windows-10 tag, hardly any traffic at all. – Braiam Nov 16 '15 at 1:45
  • Sure; Lets not do anything. Put our heads in the sand. Whatever. I am done with this community. 3000 questions in a year about Windows 10 is obviously nothing – Ramhound Nov 16 '15 at 2:08
1

Aren't they all using Windows 10 anyways? Why must we use the reductio ad absurdum with tags when there isn't any actual gain for asker and answerers? People can't even tell whenever their question is applicable to only one or another version, nor should we hope they know, which would just put more pressure on knowledgeable to fix the tagging (or at least, try to), without any actual benefit of such chore. And guess what, they will not replace the tags, anyways.

In the end Microsoft will push forward the update/upgrade to all their users for "security reasons" and the point will be reduced moot by then. Answerers should just presume the asker is using any version of it, and answer with the method is applicable for all iterations. I mean, installing software would be the same for years to come, no?


Someone created the , here's the results:

All in all, none of these questions benefits from having an extra tag, and in those cases where it would make sense, the issue isn't even related.

  • @Ramhound but, why should we care about them? Windows 10 tag gets at most ~2 questions day, it isn't even overloaded. Futher categorization (or more accurately: just because) doesn't make answerers find questions easier, and as I said before, there's simply no benefit on doing so. – Braiam Nov 16 '15 at 1:43
  • @Ramhound but, will be impossible with 1511+ builds? No. That's why the [version specific tags] guideline says: I would only use version tags when the question content is irrevocably tied to a specific version of something and can never be relevant to earlier versions or later versions. It isn't expected that later versions of Windows 10 not to be able to do this (or do you have insider information?). – Braiam Nov 18 '15 at 20:30
  • @Ramhound but why should they be separated from the general Windows 10 herd? If I ask the question the answer could be: if you are using X version you can't, unlike people using Y version, which can do it this way. See? There is less information duplication and all the information is in a single Q&A pair. Further separation is not needed, is counterproductive. Users shouldn't have to ask several questions for each interaction of any piece of software, that's why there's a bounty reason that reads: The current answer(s) are out-of-date and require revision given recent changes. – Braiam Nov 18 '15 at 21:58
  • You are right. It shouldn't be separated. – Ramhound Nov 18 '15 at 21:59

You must log in to answer this question.

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