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

Update PR template for release process #2041

Merged
merged 4 commits into from
Aug 23, 2018
Merged

Conversation

cwgoes
Copy link
Contributor

@cwgoes cwgoes commented Aug 15, 2018

For Admin Use:

  • Added appropriate labels to PR (ex. wip, ready-for-review, docs)
  • Reviewers Assigned
  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

@codecov
Copy link

codecov bot commented Aug 15, 2018

Codecov Report

Merging #2041 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #2041   +/-   ##
========================================
  Coverage    64.86%   64.86%           
========================================
  Files          115      115           
  Lines         6862     6862           
========================================
  Hits          4451     4451           
  Misses        2127     2127           
  Partials       284      284

Copy link
Contributor

@rigelrozanski rigelrozanski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is too verbose to add into the PR template (4 lines for one concept is a lot) - I think this should instead be added to CONTRIBUTING.md. Maybe having just the first line Targeted PR against correct branch and have it linked to the section in CONTRIBUTING could make sense

@cwgoes
Copy link
Contributor Author

cwgoes commented Aug 22, 2018

I think this is too verbose to add into the PR template (4 lines for one concept is a lot) - I think this should instead be added to CONTRIBUTING.md. Maybe having just the first line Targeted PR against correct branch and have it linked to the section in CONTRIBUTING could make sense

OK; so updated.

@@ -4,6 +4,11 @@ v Before smashing the submit button please review the checkboxes.
v If a checkbox is n/a - please still include it but + a little note why
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->

- Targeted PR against correct branch:
- `release/vxx.yy.zz` for a merge into a release candidate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're going to list this in the pr template we should give more direction as to what prs go into the release. If we don't, then this shouldn't go in the template imo

### PR Targeting

Ensure that you base and target your PR on the correct branch:
- `release/vxx.yy.zz` for a merge into a release candidate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're going to list this in the CONTRIBUTING.md we should give more direction as to what prs go into the release. Right now this basically just states what the main branches are, not which PR's should go where.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a paragraph to explain which PRs should go where.

@cwgoes cwgoes merged commit efe3d3c into develop Aug 23, 2018
@cwgoes cwgoes deleted the cwgoes/clarify-release-process branch August 23, 2018 13:42
chillyvee pushed a commit to chillyvee/cosmos-sdk that referenced this pull request Mar 1, 2024
* Upgrade to v9

* Update handler

* Fix linter

* Remove old or basic upgrades from codecov

* add execute rights to test scripts (cosmos#2041)

* Add e2e tests

* Update code smell

* Remove and refactor duplicated query exec

* Fix linter

* Update ICS dependency

* Update dependency

* Fix typo

Co-authored-by: Simon Noetzlin <[email protected]>

Co-authored-by: MSalopek <[email protected]>
Co-authored-by: Simon Noetzlin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants