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

Setup develop branch #29

Open
yoshikinoko opened this issue Oct 15, 2019 · 0 comments
Open

Setup develop branch #29

yoshikinoko opened this issue Oct 15, 2019 · 0 comments
Assignees

Comments

@yoshikinoko
Copy link
Contributor

This is just an idea. But I'm always afraid to create PR for the master branch.

According to A successful Git branching model, the master branch should point out the latest release.

We consider origin/master to be the main branch where the source code of HEAD always reflects a production-ready state.

Expected Behaviour

Keep the master branch as same as the latest release on npm.
and use the develop branch for future release

Actual Behaviour

xdpm does not have develop branch

Reproduce Scenario (including but not limited to)

N/A

Steps to Reproduce

N/A

Platform and Version

N/A

Sample Code that illustrates the problem

N/A

Logs taken while reproducing problem

N/A

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

No branches or pull requests

3 participants