RFC0004-PowerShell-Module-Versioning

PowerShell / PowerShell-RFC

RFC (Request for Comments) documents for community feedback on design changes and improvements to PowerShell ecosystem

MIT License

423 stars 121 forks source link

RFC0004-PowerShell-Module-Versioning #10

Open joeyaiello opened 8 years ago

joeyaiello commented 8 years ago

Use this issue to comment on this RFC: https://github.com/PowerShell/PowerShell-Language-RFC/blob/master/1-Draft/RFC0004-PowerShell-Module-Versioning.md

Jaykul commented 6 years ago

Since @SphenicPaul woke this thread up, it's worth saying:

In PowerShell 6 we have [System.Management.Automation.SemanticVersion], and the PowerShell releases are using SemVer, and we've already changed $PSVersionTable.PSVersion --how far are we from supporting it in module versions?

joeyaiello commented 5 years ago

@PowerShell/powershell-committee has been working to drive down our RFC debt. Here are the notes that resulted out a meeting on this one:

Non-binding set of guidelines for us and the community to follow
We all agree that most of this has already been implemented
A big chunk has also been addressed by the PreRelease flag in PowerShellGet
- This includes previews of major version updates
RFC needs to be updated to reflect the current state of the world
- new behavior should be implemented in additional RFCs /cc @SydneyhSmith

joeyaiello commented 5 years ago

@PowerShell/powershell-committee agrees that the above is accurate

SydneyhSmith commented 5 years ago

The specification here matches our recommendations for PowerShell Module Versioning in the PowerShell Documentation

joeyaiello commented 5 years ago

@SydneyhSmith Ideally, we'd like the merged PR for this to be as up-to-date as the docs you listed. Would you mind making those changes? Thanks!