-
Notifications
You must be signed in to change notification settings - Fork 525
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.
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
Contribution guide updates for Quickstart authors #977
base: release-1.14
Are you sure you want to change the base?
Conversation
…ics. Signed-off-by: Paul Yuknewicz <[email protected]>
Started reviewing this... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @paulyuk In the pull request for changing .net version that I recently submitted, you asked me to base my changes on a release-1.XX branch of the repo. Is this something worth mentioning in the CONTRIBUTING.md
file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments
|
||
### Cutting a release of quickstarts | ||
1. Change to the release branch created above. | ||
2. Make sure the matching runtime and CLI versions are set to match intent in `global.env` file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you point to where this file is.
TODO | ||
|
||
### Authoring tests for new Quickstarts | ||
TODO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this is a community call recording can add a link here
2. Make sure the matching runtime and CLI versions are set to match intent in `global.env` file | ||
3. Create a new [Tag](https://github.com/dapr/quickstarts/tags) from this release branch in the form of v.M.mm-rcN, e.g. `v1.13-rc1`. | ||
4. After the final RC is promoted to a full release, create a new Tag dropping the RC, e.g. `v1.13.0`. | ||
5. Create a new [Release]() in the form of `v1.13` and reference the tag from last step. Note the releases have convention of no dot releases (e.g. v1.13.0) unless patched (e.g. v1.13.1). Include highlights and changelist in the release notes, and double check that contributors get credit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Brackets are empty for Release
- What are you saying here "Note the releases have convention of no dot releases (e.g. v1.13.0) unless patched (e.g. v1.13.1)" - do not understand the "no dot releases" reference here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will clarify that sentence. good catch.
1. Commit your changes and open a PR to the Dapr Quickstarts repository. | ||
1. Wait for the CI process to finish and make sure all checks are green. | ||
1. A maintainer of the project will be assigned, and you can expect a review within a few days. | ||
1. Make sure the checks/test actions pass with your changes. See [Test authoring] for information around how this works and how to troubleshoot. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See [Test authoring] - Needs a URL reference
Co-authored-by: Mark Fussell <[email protected]> Signed-off-by: Paul Yuknewicz <[email protected]>
Co-authored-by: Mark Fussell <[email protected]> Signed-off-by: Paul Yuknewicz <[email protected]>
Co-authored-by: Mark Fussell <[email protected]> Signed-off-by: Paul Yuknewicz <[email protected]>
Co-authored-by: Mark Fussell <[email protected]> Signed-off-by: Paul Yuknewicz <[email protected]>
Description
Expand the CONTRIBUTING guide with:
Issue reference
We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #967
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: