Repository navigation
Master builds produce artifacts with '6.0.0.-rc' versioning instead of '6.1.0-preview.1' #5497
Description
If I understood correctly from the last community call, the master branch is now for 6.1.0 development.
However, the artifcats of master builds are versioned as 6.0.0.-rc. See e.g. here for an example of the latest build.
Info: Latest commit of master as of November 18: cb048ea9f4f7ccc3612141ee76f7937b9ca1c823
Activity
iSazonov commentedon Nov 18, 2017
We still are in RC stage not GA.
bergmeister commentedon Nov 18, 2017
I thought that is what the 6.0.0 branch was for? Steve's blog post here also said:
SteveL-MSFT commentedon Nov 18, 2017
When we merged the changes from the RC release branch back to master, we merged everything including the version string. Master should be 6.1.0-beta.1 while 6.0.0 continues on the Release branch. cc Dongbo Wang (@daxian-dbw)
[-]Master builds produce artifacts with '6.0.0.-rc' versioning instead of '6.1.0'[/-][+]Master builds produce artifacts with '6.0.0.-rc' versioning instead of '6.1.0-beta.1'[/+]iSazonov commentedon Nov 18, 2017
Steve Lee (@SteveL-MSFT) In blog post the branch link is broken in "we also created a branch for the eventual PowerShell Core 6.0.0 final release. " I see Release branch renamed to 6.0.0.
SteveL-MSFT commentedon Nov 19, 2017
Ilya (@iSazonov) thanks for catching that, fixed.
bergmeister commentedon Nov 19, 2017
Steve Lee (@SteveL-MSFT) Would it make sense to rather use the word
previewinstead ofbetastarting from6.1since .Net Core and the Visual Studio family use that term as well? Also,previewindicates that it is just the bleeding edge version of something that already had RTM quality, which differentiates it from the past 6.0 betas.SteveL-MSFT commentedon Nov 19, 2017
Christoph Bergmeister (@bergmeister) agree,
previewcaptures it better as being incomplete thanbetawhich implies subpar quality[-]Master builds produce artifacts with '6.0.0.-rc' versioning instead of '6.1.0-beta.1'[/-][+]Master builds produce artifacts with '6.0.0.-rc' versioning instead of '6.1.0-preview.1'[/+]iSazonov commentedon Nov 20, 2017
Based On SymVer 2.0 and modern life cycle we could give up on "beta" and "preview" and use 6.1.x on a daily basis.
Related #5477
bergmeister commentedon Nov 20, 2017
Ilya (@iSazonov) SemVer 2.0 states that the 3rd number should only be for patches