Timeline for Should there be a V6 Specific Powershell Tag
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2018 at 18:20 | comment | added | music2myear | We may wish to synonimize powershell-core and powershell-v6.0 as they currently refer to the same thing. Though I suppose, depending on what happens with PowerShell 7, that may need to be reversed eventually. | |
| May 30, 2018 at 18:12 | comment | added | music2myear | I've created the powershell-6.0 tag. | |
| May 18, 2018 at 19:08 | comment | added | Bewc | I looked for a v6 tag on a question I just asked (superuser.com/questions/1324007/…), didn't find one, and was going to ask on meta, when I found this. I don't have the rep yet to create tags. @EBGreen can you create it now? | |
| May 9, 2018 at 7:05 | comment | added | fixer1234 | There is no V6 tag yet. You can't just create a tag, it needs to be associated with at least one question. I checked for existing Powershell questions and found only one so far that contained a reference to V6: superuser.com/questions/1320481/powershell-6-missing-cmdlets. You can create one on that question or wait for the next V6 question and add it there. At least one more question needs to be tagged within 6 months or the tag turns into a pumpkin. | |
| May 8, 2018 at 12:51 | comment | added | Burgi | There are already specific version tags. See the following: powershell-5.0, powershell-4.0, powershell-3.0 | |
| May 8, 2018 at 12:33 | history | asked | EBGreen | CC BY-SA 4.0 |