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

docs(readme): update readme file #5092

Merged
merged 2 commits into from
Oct 27, 2019
Merged

Conversation

dzhavat
Copy link
Contributor

@dzhavat dzhavat commented Oct 18, 2019

Update the main readme file

Description:
Since there's no stable branch, I thought using the 6.x will be more correct.

And I've also copied a line from 5.x branch about making PRs. I've seen at least one person asking for this in a comment. Another option could be adding that line to the PR template.

Related issue (if exists):

README.md Outdated
- [master](https://github.com/ReactiveX/rxjs/commits/master) - This is all of the current, unreleased work, which is against v7 of RxJS right now
- [stable](https://github.com/ReactiveX/rxjs/tree/6.x) - This is the branch for the latest version you'd get if you do `npm install rxjs`

Most PRs should be made to **master**, unless you know it is a breaking change.
Copy link
Collaborator

@cartant cartant Oct 26, 2019

Choose a reason for hiding this comment

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

I think we can remove the "unless you know it is a breaking change".

TBH, that makes no sense to me: there are two branches listed here and this implies that if the submitter knows it's a breaking change it should target ... stable? 🤷‍♂

IMO, it should just say "Most PRs should be made to master."

My understanding is that we change the branch to which master refers to manage this. E.g. until fairly recently, master was the 6.x branch, but now that the version 7 release is imminent, we want PRs to target version 7, so that's the master branch. Contributors should almost always target master because we configure master to be the branch to which PRs should be targeted.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Makes sense. Just made the change :)

@cartant cartant merged commit 52fc393 into ReactiveX:master Oct 27, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants