-
Notifications
You must be signed in to change notification settings - Fork 9
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
Development branch #278
Comments
Yes, I have been thinking exactly this for a few days now. We can do several things to organize our dev side:
Proposal
Let me know if you think something else! (probably 😄) |
@vankesteren Yes, agree mostly with the proposal. One thing I would change:
I'm fine with working in forks, it has been a while! |
Yeah, just to keep the repo clean you know, so i dont have to go and delete stale branches every other week 😛 |
I don't think that would be my most important reason, but I suppose we should follow the leave-no-trace principle! |
Let's do this as well with our optional dependencies: |
I have asked again for some feedback on metasyn (in terms of documentation). One thing that stood out was that the documentation is currently ahead of the code, so that it doesn't work correctly when you follow the new instructions with the old code (on PyPi). While we can make more releases, another solution would be to start using development branches. We would only merge to the main branch during a release. What are your thoughts?
The text was updated successfully, but these errors were encountered: