docs: Further improve Release docs #9925
Merged
Conversation
This file contains 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
Includes proposal of a new versioning scheme and more accurate representation of the release candidate process.
tofumatt
commented
Sep 14, 2018
|
|
||
| ### Writing the Release Post and Changelog | ||
|
|
||
| 1. Open the [list of closed pull requests](https://github.com/WordPress/gutenberg/pulls?utf8=✓&q=is%3Apr+is%3Aclosed+sort%3Acreated-desc+) and filter by the current milestone. |
There was a problem hiding this comment.
This will only work once we get an auto-tagging milestone bot: #9239
gziolo
approved these changes
Oct 17, 2018
| # Do a dry run of the repository reset. Prompting the user for a list of all | ||
| # files that will be removed should prevent them from losing important files! | ||
| status "Resetting the repository to pristine condition. ✨" | ||
| git clean -xdf --dry-run | ||
| warning "🚨 About to delete everything above! Is this okay? 🚨" | ||
| echo -n "[Y]es/[N]o: " | ||
| echo -n "[y]es/[N]o: " |
There was a problem hiding this comment.
It should be lowercase for N, too? :)
There was a problem hiding this comment.
No is the default, so it's uppercase 😄
|
These docs include the notion we should be labelling |
aduth
reviewed
Apr 1, 2019
| @@ -1,4 +1,4 @@ | |||
| Gutenberg's deprecation policy is intended to support backwards-compatibility for two minor releases, when possible. The current deprecations are listed below and are grouped by _the version at which they will be removed completely_. If your plugin depends on these behaviors, you must update to the recommended alternative before the noted version. | |||
There was a problem hiding this comment.
Was this supposed to be removed without a replacement? It currently reads awkwardly as "intended to support compatibility for releases". I don't think it should have been removed.
Edit: I propose adding back in #14756
This was referenced Apr 1, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Includes proposal of a new versioning scheme and more accurate representation of the release candidate process.
This includes a proposal to move away from versioning what are, in effect, major releases with minor release bumps that reset at
3.9>4.0. In the future we should just do something like what Firefox or React do and increment major versions at every "release".This would be closer to semantic versioning as we shouldn't be deprecating things with minor versions, but code marked as deprecated in
3.6gets removed by3.9.Since
4.0is upcoming anyway I figured now is a great time to make the change. DISCUSS! 😉