From 35ed2ff24b50359e06f09fb73357563fd2be5b13 Mon Sep 17 00:00:00 2001 From: jkeithb Date: Mon, 4 Dec 2017 12:54:52 -0800 Subject: [PATCH 1/2] Changed required PSGet version to 1.6.0 --- gallery/psget/module/PreReleaseModule.md | 2 +- gallery/psget/script/PreReleaseScript.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gallery/psget/module/PreReleaseModule.md b/gallery/psget/module/PreReleaseModule.md index 2cab01caac92..cf4f0ca1d800 100644 --- a/gallery/psget/module/PreReleaseModule.md +++ b/gallery/psget/module/PreReleaseModule.md @@ -7,7 +7,7 @@ title: PrereleaseModule --- # Prerelease Module Versions -Starting with version 1.5.0, PowerShellGet and the PowerShell Gallery provide support for tagging versions greater than 1.0.0 as a prerelease. Prior to this feature, prerelease items were limited to having a version beginning with 0. The goal of these features is to provide greater support for [SemVer v1.0.0](http://semver.org/spec/v1.0.0.html) versioning convention without breaking backwards compatibility with PowerShell versions 3 and above, or existing versions of PowerShellGet. This topic focuses on the module-specific features. The equivalent features for scripts are in the [Prerelease Versions of Scripts](../script/PrereleaseScript.md) topic. Using these features, publishers can identify a module or script as version 2.5.0-alpha, and later release a production-ready version 2.5.0 that supersedes the prerelease version. +Starting with version 1.6.0, PowerShellGet and the PowerShell Gallery provide support for tagging versions greater than 1.0.0 as a prerelease. Prior to this feature, prerelease items were limited to having a version beginning with 0. The goal of these features is to provide greater support for [SemVer v1.0.0](http://semver.org/spec/v1.0.0.html) versioning convention without breaking backwards compatibility with PowerShell versions 3 and above, or existing versions of PowerShellGet. This topic focuses on the module-specific features. The equivalent features for scripts are in the [Prerelease Versions of Scripts](../script/PrereleaseScript.md) topic. Using these features, publishers can identify a module or script as version 2.5.0-alpha, and later release a production-ready version 2.5.0 that supersedes the prerelease version. At a high level, the prerelease module features include: diff --git a/gallery/psget/script/PreReleaseScript.md b/gallery/psget/script/PreReleaseScript.md index 6994325405d2..b9563f39fdd1 100644 --- a/gallery/psget/script/PreReleaseScript.md +++ b/gallery/psget/script/PreReleaseScript.md @@ -8,7 +8,7 @@ title: PrereleaseScript # Prerelease Versions of Scripts -Starting with version 1.5.0, PowerShellGet and the PowerShell Gallery provide support for tagging versions greater than 1.0.0 as a prerelease. Prior to this feature, prerelease items were limited to having a version beginning with 0. The goal of these features is to provide greater support for [SemVer v1.0.0](http://semver.org/spec/v1.0.0.html) versioning convention without breaking backwards compatibility with PowerShell versions 3 and above, or existing versions of PowerShellGet. +Starting with version 1.6.0, PowerShellGet and the PowerShell Gallery provide support for tagging versions greater than 1.0.0 as a prerelease. Prior to this feature, prerelease items were limited to having a version beginning with 0. The goal of these features is to provide greater support for [SemVer v1.0.0](http://semver.org/spec/v1.0.0.html) versioning convention without breaking backwards compatibility with PowerShell versions 3 and above, or existing versions of PowerShellGet. This topic focuses on the script-specific features. The equivalent features for modules are in the [Prerelease Module Versions](../module/PrereleaseModule.md) topic. Using these features, publishers can identify a script as version 2.5.0-alpha, and later release a production-ready version 2.5.0 that supersedes the prerelease version. At a high level, the prerelease script features include: From 06d6bd81189c1062b7205e19170d8271bcb8baa6 Mon Sep 17 00:00:00 2001 From: jkeithb Date: Fri, 8 Dec 2017 11:30:49 -0800 Subject: [PATCH 2/2] Fixes to PSGet TOC and WMF 5.1 compat page --- gallery/TOC.md | 3 ++- wmf/5.1/productincompat.md | 4 +++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/gallery/TOC.md b/gallery/TOC.md index dadea276e34c..27e3168f84e9 100644 --- a/gallery/TOC.md +++ b/gallery/TOC.md @@ -39,6 +39,7 @@ ### [Publish](psget/module/psget_publish-module.md) ### [Modules with PSEditions](psget/module/modulewithpseditionsupport.md) ### [Modules Requiring License Acceptance](psget/module/RequireLicenseAcceptance.md) +### [Prerelease Versions](psget/module/PreReleaseModule.md) ### [Troubleshooting](psget/psget_cmdlets_troubleshooting.md) ## Script @@ -54,7 +55,7 @@ ### [Publish](psget/script/psget_publish-script.md) ### [Scripts with PSEditions](psget/script/scriptwithpseditionsupport.md) ### [Require License Acceptance for Scripts](psget/script/script_RequireLicenseAcceptance.md) - +### [Prerelease Versions](psget/script/PreReleaseScript.md) ## Repository management ### [Bootstrapping NuGet provider and NuGet.exe](psget/repository/bootstrapping_nuget_proivder_and_exe.md) ### [Registering repository](psget/repository/psget_register-psrepository.md) diff --git a/wmf/5.1/productincompat.md b/wmf/5.1/productincompat.md index c5aa832dca9a..fd1154a578ae 100644 --- a/wmf/5.1/productincompat.md +++ b/wmf/5.1/productincompat.md @@ -11,10 +11,12 @@ keywords: wmf,powershell,setup > Systems that are running the following server applications **can run** Windows Management Framework 5.1: - Microsoft SharePoint Server 2013 -- Skype for Business Server 2015 +- Skype for Business Server 2015 (_See Note_) - Microsoft Lync Server 2013 - System Center 2012 Configuration Manager +_Note: Skype for Business Server 2015 compatibility with WMF 5.1 has been tested only with Windows Server 2012 R2._ + ## Not Tested: > Systems that are running the following server applications **have not tested** against Windows Management Framework 5.1: