-
Notifications
You must be signed in to change notification settings - Fork 246
add CONTRIBUTING guidelines and initial changelogs #249
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
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
a7e3fac
add CONTRIBUTING guidelines and initial changelogs
ordian 9d58f1d
Update CONTRIBUTING.md
ordian 5e30457
[CONTRIBUTING] address some of the review comments
ordian 69ff0e6
[CONTRIBUTING] mention our code style
ordian df9c821
rustfmt (sorry not sorry)
ordian eae6a3b
unscrew uint macros fmt
ordian 50ed355
rustfmt: max width 120
ordian b10ffee
rustfmt: use_small_heuristics = "Max"
ordian 87db8df
fix CI
ordian e00cbad
argh
ordian a517a01
CONTRIBUTING: mention gitter
ordian 3fd73cb
impl-serde: bump to 0.2.3
ordian 515c75e
Merge branch 'master' into ao-contributing-guidelines
ordian 6a33a17
Revert "impl-serde: bump to 0.2.3"
ordian 7f946ce
fmt
ordian 444ce01
impl-serde: update changelog for 0.2.3
ordian File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
| # Contributing to parity-common | ||
|
|
||
| parity-common welcomes contribution from everyone in the form of suggestions, bug | ||
| reports, pull requests, and feedback. This document gives some guidance if you | ||
| are thinking of helping us. | ||
|
|
||
| Please reach out here in a GitHub issue or in the parity channel on [gitter] if we can do anything to help you contribute. | ||
|
|
||
| [gitter]: https://gitter.im/paritytech/parity | ||
|
|
||
| ## Submitting bug reports and feature requests | ||
|
|
||
| When reporting a bug or asking for help, please include enough details so that | ||
| the people helping you can reproduce the behavior you are seeing. For some tips | ||
| on how to approach this, read about how to produce a [Minimal, Complete, and | ||
| Verifiable example]. | ||
|
|
||
| [Minimal, Complete, and Verifiable example]: https://stackoverflow.com/help/mcve | ||
|
|
||
| When making a feature request, please make it clear what problem you intend to | ||
| solve with the feature, any ideas for how parity-common could support solving that problem, any possible alternatives, and any disadvantages. | ||
|
|
||
| ## Versioning | ||
|
|
||
| As many crates in the rust ecosystem, all crates in parity-common follow [semantic versioning]. This means bumping PATCH version on bug fixes that don't break backwards compatibility, MINOR version on new features and MAJOR version otherwise (MAJOR.MINOR.PATCH). Versions < 1.0 are considered to have the format 0.MAJOR.MINOR, which means bumping MINOR version for all non-breaking changes. | ||
|
|
||
| If you bump a dependency that is publicly exposed in a crate's API (e.g. `pub use dependency;` or `pub field: dependency::Dependency`) and the version transition for the dependency was semver-breaking, then it is considered to be a breaking change for the consuming crate as well. To put it simply, if your change could cause a compilation error in user's code, it is a breaking change. | ||
|
|
||
| Bumping versions should be done in a separate from regular code changes PR. | ||
|
|
||
| [semantic versioning]: https://semver.org/ | ||
|
|
||
| ## Releasing a new version | ||
|
|
||
| This part of the guidelines is for parity-common maintainers. | ||
|
|
||
| When making a new release make sure to follow these steps: | ||
|
ordian marked this conversation as resolved.
|
||
| * Submit a PR with a version bump and list all major and breaking changes in the crate's changelog | ||
|
|
||
| After the PR is merged into master: | ||
| * `cargo publish` on the latest master (try with `--dry-run` first) | ||
| * Add a git tag in format `<crate-name>-v<version>`, | ||
| e.g. `git tag impl-serde-v0.2.2` and push it with `git push origin impl-serde-v0.2.2` | ||
|
|
||
| ## Conduct | ||
|
|
||
| We follow [Substrate Code of Conduct]. | ||
|
|
||
| [Substrate Code of Conduct]: https://github.com/paritytech/substrate/blob/master/CODE_OF_CONDUCT.adoc | ||
|
|
||
| ## Attribution | ||
|
|
||
| This guideline is adapted from [Serde's CONTRIBUTING guide]. | ||
|
|
||
| [Serde's CONTRIBUTING guide]: https://github.com/serde-rs/serde/blob/master/CONTRIBUTING.md | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| # Changelog | ||
|
|
||
| The format is based on [Keep a Changelog]. | ||
|
|
||
| [Keep a Changelog]: http://keepachangelog.com/en/1.0.0/ | ||
|
|
||
| ## [Unreleased] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| # Changelog | ||
|
|
||
| The format is based on [Keep a Changelog]. | ||
|
|
||
| [Keep a Changelog]: http://keepachangelog.com/en/1.0.0/ | ||
|
|
||
| ## [Unreleased] | ||
|
|
||
| ## [0.8.1] - 2019-10-24 | ||
| ### Dependencies | ||
| - Updated dependencies (https://github.com/paritytech/parity-common/pull/239) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| # Changelog | ||
|
|
||
| The format is based on [Keep a Changelog]. | ||
|
|
||
| [Keep a Changelog]: http://keepachangelog.com/en/1.0.0/ | ||
|
|
||
| ## [Unreleased] | ||
| ### Added | ||
| - uint error type is re-exported (https://github.com/paritytech/parity-common/pull/244) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Worth mentioning the exception of
serdethat isn't following semver? Caution againstrandupgrades?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.
Not sure what to add here. Although
serdedoesn't follow semver forminorandpatchbumping, it will bumpmajoron a breaking change. And not sure howrandis different in terms of breaking changes from other crates. But open to any suggestions.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.
serde: so you're saying we don't need to mention it not following semver becauseminor/patchreleases are backwards compatible?rand: my thinking was simply that some crate updates are (much) more risky than others, but it's hard to come out and say "don't send PRs to upgraderand` because it's a mess". But I guess we can handle that as/if PRs come in.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.
yep, pretty much