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

Any reason why 'old' branch is set to default? #46

Open
antoniomtz opened this issue Nov 5, 2018 · 4 comments
Open

Any reason why 'old' branch is set to default? #46

antoniomtz opened this issue Nov 5, 2018 · 4 comments

Comments

@antoniomtz
Copy link

Is there any reason why the "old" branch is set as default?
I see that "Master" has support of Dep, but not in "old".

@sapk
Copy link
Owner

sapk commented Nov 5, 2018

I try to rework all my plugins to have a common base. But this is not currently working and haven't take time for this project so I set old as the default.

@sapk
Copy link
Owner

sapk commented Nov 5, 2018

@antoniomtz
Copy link
Author

Yes, I see you where using Basic and Driver pkgs in Master already.
I was planning to work on #5 but right now all the PRs will go to 'old' branch.
What would be the best approach right now?

@sapk
Copy link
Owner

sapk commented Nov 5, 2018

I would say it depends if it is a fix you can send it to old if a feature or want to make master work to master.

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

2 participants