-
Notifications
You must be signed in to change notification settings - Fork 37
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
New Branch & Github rules #13
Comments
Sounds great! Let's see - so as we discussed on Discord, I think we were looking towards some form of rolling-release schedule, similar to Rust's:
Of course this is just one potential git flow and time timescales (weeks, quarters) can be adjusted. So as for contributing guidelines and CoC, they're kinda just mashed together in CONTRIBUTING.md atm. Ideally we'd separate this out, and use some predefined CoC, like the Contributor's Covenant or something. What are your thoughts on PR/Issue templates? |
So currently, we have two primary branches:
If you're implementing a feature for the next minor release, merge the PR against |
Issue seems stale and we seem to have found a git flow that works, so I'm closing this issue. |
For the next few releases, I'd like to standardize our DevOps and release procedures (this is sort of related to #10, but a little bit more general; this is more meant to discuss the way that branches are laid out).
Additionally, I'd like to talk about what contributing guidelines, CoC, and PR/issue templates should look like.
The text was updated successfully, but these errors were encountered: