Skip to content

Test #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Test #35

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a40508e
Docs for release tagging
bganapa Jun 22, 2020
fda5e0c
Merge branch 'master' of https://github.com/azure/azurestack-powershe…
bganapa Jul 22, 2020
5cb396d
test
bganapa Jul 22, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docker/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The release containers derive from the [Powershell image][powershell image], and

[powershell image]: https://hub.docker.com/_/microsoft-powershell

AzureStack PowerShell [release notes](https://aka.ms/azspsdocker)
AzureStack PowerShell [release notes](https://aka.ms/azspsdockerreadme)

## Examples

Expand Down
19 changes: 19 additions & 0 deletions docs/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
## Release Process
Releasing the modules to TestGallery and then further to PSGallery is currently manual and gated through Azure SDK release process.

The process will be automated with a release pipeline in devops

### Release Notes
The release notes are updated in each module's PSData secction of the Psd1. It is recommended to have a aka.ms link in each AzureStack module release so that the notes could be updated for clarity, breaking changes etc.. at a later time

### Tagging
Each release gets tagged once the final build is verified. In future, the release pipeline will automatically create the tag. Right now the tag is created manually. The tag can be created once the bits are in TestGallery

git tag v2.0.1-preview
git push upstream v2.0.1-preview

### Draft a release
Please follow the github help link for instructions
https://help.github.com/en/github/administering-a-repository/managing-releases-in-a-repository