docs: add link to README of stable version#358
Merged
Conversation
ctavan
force-pushed
the
back-to-trunk-based-development
branch
from
3c1f96d to
6cabebf
Compare
Member
|
Sounds good. Re: having next release as v4 vs. v6, if you're going to do that, then just go with v7 to avoid possible confusion with the "v6" RFC UUID idea we've been bandying about. |
broofa
approved these changes
Jan 28, 2020
ctavan
force-pushed
the
back-to-trunk-based-development
branch
from
6cabebf to
266bc81
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@broofa I would like to merge the next branch into master now and revert to trunk-based development. Having the two diverging branches already starts to cause some headache and I would like to avoid that.
I would therefore add a notice to the Readme that points to the current "stable" readme until we release the next major version of this library and then go ahead and merge the
nextbranch intomaster.I would then release the first canary prerelease of the new major version for folks to try out.
I was considering to release it as
v6.0.0instead ofv4.0.0in order to avoid any potential confusion aroundv3/v4/v5uuids.WDYT?