-
Notifications
You must be signed in to change notification settings - Fork 1k
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
dev -> master When to merge ? #871
Comments
Yeah, merge dev is really overdue. Next month I should have some time (I'd like to do some improvements on voice control). Then I would suggest, merge in August?
Yes, I'll take care of the diffs - I don't think that's a major problem. I would suggest, handle master and if dev is ready to merge, I'll just "backport" everything on master ;). |
I'm late. But it's still August ;) A preview what I did so far: https://github.com/pnhofmann/Jarvis/commits/dev OK, now everything I decided I want to change is implemented. But I know: Lots of stuff is still a bit broken. So I'll do testing the next days. Guess, I'll need ~2 weeks and then I'll write again. |
What's going on with this? Was dev originally planned to be the branch that all PR's would be made to and master would have the stable release? |
Hi @Milind220 Maybe, if you do stuff like in #913 (any improvements really appreciated ;) ) - consider switching to dev ;). |
Soon |
Maybe we can discuss here when it would be appropriate to merge the dev branch to master.
I'm thinking:
Thoughts @pnhofmann. We can tag other collaborators for more thoughts as well.
The text was updated successfully, but these errors were encountered: