PowerShellStandard icon indicating copy to clipboard operation
PowerShellStandard copied to clipboard

PowerShellStandard library nuget package name is problematic

Open JamesWTruher opened this issue 6 years ago • 2 comments

the current name of the standard library has some issues with regard to the upcoming PowerShell 7 release. We should consider renaming the library to PowerShellStandard.Library.7.0.0 to show the terminus rather than the initial supported version, especially in the light that PowerShell 6 will not remain supported long term.

JamesWTruher avatar Oct 03 '19 23:10 JamesWTruher

So the library name will have the end version and then the version will be the initial version? Am I understanding that right?

Or will we version based on the ending version? if so, what's the initial version?

TylerLeonhardt avatar Oct 04 '19 00:10 TylerLeonhardt

PowerShell Standard is intended support a subset of Windows PowerShell and PowerShell Core versions.

In the past, the version of Standard (3.0 and 5.1) was tied to the floor version in the pair (Windows PowerShell). Given that all future version of Standard will only guarantee compatibility back to 5.1, that version nomenclature makes no sense anymore.

And given that new APIs are being added back to 7.x, we want to use the version now to say "this works with Windows PS 5.1 and PowerShell Core <version of Standard library>" (in this case 7.0).

In the future, a Std 7.1 would guarantee support with 5.1 and 7.1

joeyaiello avatar Oct 11 '19 22:10 joeyaiello