Skip to content
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

Draft
wants to merge 9 commits into
base: release-1.14
Choose a base branch
from

Conversation

paulyuk
Copy link
Contributor

@paulyuk paulyuk commented Feb 6, 2024

Description

Expand the CONTRIBUTING guide with:

  • Steps to make RC and final releases
  • Steps to author a new Quickstart
  • Steps to author MMD tests
  • Steps to troubleshoot common issues with tests

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:

  • The quickstart code compiles correctly
  • You've tested new builds of the quickstart if you changed quickstart code
  • You've updated the quickstart's README if necessary
  • If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

…ics.

Signed-off-by: Paul Yuknewicz <paulyuk@Pauls-MacBook-Pro-2.local>
@paulyuk paulyuk self-assigned this Feb 6, 2024
@paulyuk paulyuk added this to the 1.13 milestone Feb 6, 2024
@paulyuk paulyuk marked this pull request as draft February 6, 2024 19:11
@paulyuk paulyuk changed the base branch from master to release-1.13 February 11, 2024 21:03
@paulyuk paulyuk added documentation Improvements or additions to documentation P1 labels Feb 11, 2024
@rabollin
Copy link
Contributor

Started reviewing this...

Copy link
Contributor

@pngan pngan left a 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?

Copy link
Member

@msfussell msfussell left a 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
Copy link
Member

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.

CONTRIBUTING.md Outdated Show resolved Hide resolved
TODO

### Authoring tests for new Quickstarts
TODO
Copy link
Member

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

CONTRIBUTING.md Outdated Show resolved Hide resolved
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.
Copy link
Member

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

Copy link
Contributor Author

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.

CONTRIBUTING.md Outdated Show resolved Hide resolved
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.
Copy link
Member

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

CONTRIBUTING.md Outdated Show resolved Hide resolved
paulyuk and others added 5 commits July 23, 2024 12:45
Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Paul Yuknewicz <paulyuk@microsoft.com>
Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Paul Yuknewicz <paulyuk@microsoft.com>
Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Paul Yuknewicz <paulyuk@microsoft.com>
Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Paul Yuknewicz <paulyuk@microsoft.com>
@paulyuk paulyuk changed the base branch from release-1.13 to release-1.14 July 25, 2024 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation P1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Contribution guide for Quickstart
5 participants