-
[This document](https://docs.google.com/document/d/1Piv8WVs0RJXLgYlj1TyXGKRWnuQ--dmzq5fBWNQ8BzE/edit) describes the branching strategy for designs that have reached the [M5 Final Release](https://open…
-
We need to figure out how we're going to handle branching going forward. For the immediate future we plan to keep `master` as 1.1, but we will need to figure out how we want to handle breaking changes…
-
Create a document that outlines the agreed upon processes of the developers of the project.
-
-
Branching is often a complex process where a lot of PRs are made. It's easy to lose track of them and a board can help.
We've been experimenting with this, but it should become part of the procedur…
ekohl updated
1 month ago
-
As part of the full package review (#33) the dots (`...`) were removed from the simulation functions (`sim_linelist()`, `sim_outbreak()` and `sim_contacts()`), as they were not used and would warn if …
-
In terms of naming branches, I would like to keep `master` as one of the mainlines so I'd propose either:
Production: `stable`
Development: `master`
Or as an alternative, we could use the mast…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues.
### Please describe the feature you have in mind and explain what the current shortcomings are?
I did some …
-
* bump-my-version version: 0.23.0
* Python version: All
* Operating System: All
### Description
We utilize Release Branching for our development lifecycle and we tag releases and patches from …
-
As our Android application grows, we need to establish a robust Git branching strategy to improve our development, testing, and release processes.
Currently, we use a maintenance branch for patches…