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

Feature Request: Separate Master (stable) & Dev branches #1017

Open
wrongecho opened this issue Aug 30, 2024 · 0 comments
Open

Feature Request: Separate Master (stable) & Dev branches #1017

wrongecho opened this issue Aug 30, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@wrongecho
Copy link
Collaborator

wrongecho commented Aug 30, 2024

We should look into using Master as the dev branch and having a separate Stable branch we periodically merge commits into once we are 100% sure they are stable.

Edits:-


Need to look into this more. It's not as simple as changing the branch in config.php as tracking has to be setup for the remote dev branch.


The easier way to do this will probably be to have master as the production/stable branch and a separate dev branch. All PRs initially go into Dev. The demo and our own instances will run dev. Once a month we will merge dev into prod. This would let us still develop fairly quickly for the majority of the month, and hopefully catch most issues before they make it into prod.

@wrongecho wrongecho added the enhancement New feature or request label Aug 30, 2024
@wrongecho wrongecho changed the title Feature Request: Separate Master (dev) & Stable branches Feature Request: Separate Master (stable) & Dev branches Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant