I have no idea what the correct policy would be. Anything that is
"accepted" into C++14 is only provisionally accepted. Until the
standard is finalized, everything in it is subject to change. (See for
example how concepts were yanked out of C++11 even after they were
mentioned all over the draft. I'd say that for now, C++1y should refer
to "all changes scheduled to be standardized later in this decade". We
can remap to C++14 or C++17 when the respective standards are
finalized (which more or less mirrors how C++0x->C++11 was handled). –
jalf 14 mins ago
I agree with jalf. We should proceed just like we did with c++0x: we kept that tag until the final draft (FDIS) was published, and only then did we start using c++11 (some people actually objected even after the FDIS, and wanted to wait until the final vote and official publication of the standard).
I think the one important thing here is that once C++14 is truly out, people searching within that tag don't want to find information that refers to behaviour that was eventually changed or cut out. That does not make the Internet better IMO. Not tagging them with c++14 until they actually cover C++14 seems important to me.
Given that, one can also argue that such questions are only applicable to a specific period of time and thus should be closed as too localized. But I don't want to go there; I suggest that anyone that wants to discuss the merits of that approach open a new question.
So, for now, I suggest the policy jalf described:
c++1y refers to all changes scheduled for standardization sometime this decade. We should use that tag since we are not discussing C++14, but merely some possible form of it. When C++14 comes out, we can finally discuss actual C++14 and not just some possible form of it, so c++14 should enter circulation. And so on for future versions.