Maintaining

Security

To be maintainer you must have 2FA enabled on accounts that give you access to DSC Community resources, for example your GitHub account and the account that access DSC Community Azure DevOps organization.

Breaking Changes

See Breaking Changes

Review

Not yet written.

Merging code

Only merge code that passes status checks, have been reviewed, and where all the review comments have be resolved and approved.

As a maintainer you are allowed to review and merge your own code. Minimum time before you as a maintainer may merge your own code is 24 hours, but it is recommended that the code is merged after 72 hours so the community has a chance to comment on the changes. Any pull request that fixes issues in a broken CI pipeline can be merged faster to unblock other pull requests. A pull request that fixes security issues is also exempted. It is recommended to use the label high priority to flag pull requests that have to be merged before the minimum 24 hour time frame.

Skip raising version

It is possible to tell the CI build pipeline (GitVersion) to not raise the version when merging a pull request, e.g. when updating the CHANGELOG.md after a release. When merging the pull request just enter +semver:skip preferably in the commit description, but also works in the commit message.

Skip CI on merge

It is possible to skip running the CI pipeline when merging a pull request, e.g. updating the CHANGELOG.md after a release. When merging the pull request just enter [skip ci] preferably in the commit description, but also works in the commit message.

Read more in Skipping CI for individual commits.

Do not add [skip ci] to a PR title, then the status checks will not run.

Prerelease

For each merge to the branch master there will be a prerelease automatically released (continuous delivery).

The version is automatically calculated in the CI pipeline based on the commit history since the previous release. The calculation is done by GitVersion and each repository has a file GitVersion.yml that controls how this calculation is performed.

The CI pipeline will create a tag in the format vX.Y.Z-previewXXXX, e.g v5.0.0-preview0001, and the prerelease to the PowerShell Gallery will have the format X.Y.Z-previewXXXX, e.g. 5.0.0-preview0001. Any consequent merges to master will make a new preview release which will be named for example 5.0.0-preview0002 and so on.

NOTE: There are an issue with module ModuleBuilder v1.0.0 and higher when using semantic version preview strings that uses a dash, e.g. fix0008-9. The string is compliant with SemVer 2.0 but there is a bug in Publish-Module that prevents the module to be released.

Release

Once the next full version should be deployed, do these steps to push a new release version tag. Important to have the correct format vX.Y.Z, e.g. v1.14.1.

Assuming ‘origin’ is the remote name pointing the upstream repository, if not then change appropriately.

# Make sure to get the latest history, use rebase to retain the linear
# commit history.
git checkout master
git fetch origin master
git rebase origin/master

git fetch origin --tags # Fetch all tags from upstream master branch
git describe --tags # To see the the latest tag, e.g. vX.Y.Z-preview0002
git tag vX.Y.Z # Creates the new version tag locally.
git push origin --tags # Push the new tag that was created locally

Avoid using git pull --tags as it also will merge (not rebase) any changes from upstream (unless already rebased). Using git pull will not retain the linear commit history.

NOTE: You could also tag a specific commit if not all commits should be released.

Update the list of resource modules

After a new resource module has been released or deprecated, please update the list of resource modules to include it on the site https://dsccommunity.org.

See the section Resource modules to learn how to update the list of resource modules.

Running the task pack locally

If the task pack´ is run locally, e.g. ´.\build.ps1 -Task pack, then nuget.exe must be updated so that it is not outdated. If it is outdated you can run into the issue PowerShell/PowerShellGet#295.

To update run the following:

# Non-admin
Invoke-WebRequest -Uri https://aka.ms/psget-nugetexe -OutFile "$env:LOCALAPPDATA\Microsoft\Windows\PowerShell\PowerShellGet\NuGet.exe"

# Admin
Invoke-WebRequest -Uri https://aka.ms/psget-nugetexe -OutFile "$env:ProgramData\Microsoft\Windows\PowerShell\PowerShellGet\NuGet.exe"

Labels

Labels are used in the issue and pull request workflows to show the current state.

These are the labels currently used by the resource modules in DSC Community. Some of these labels are meant to be used with future automation.

The script DscResourceKit-Labels that is provided by the community can be used to update the labels in a repository.

These are also set as the default organization labels so that new repositories that are created they will automatically get these labels.

Updated on 28 Jan 2019