-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Stop using develop
branch ?
#2326
Milestone
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@Progi1984, I'd like to suggest to entirely drop the
develop
branch, and instead have only a single long-lived branchmaster
. All developments can happen in short-lived "feature branch". Since we extensively use PRs already this is already very natural, and only tested PR are merged intomaster
. Thenmaster
can be released whenever it needs to.Dropping
develop
has the advantage of reduce maintenance noise. When cutting a release, there is nothing to merge anymore, so there isn't any risk of conflicts or merge mistakes. I believe it is also easier for infrequent contributors, because they only have to worry about a single remote branch.We've been working this way in PhpSpreadsheet for years now, and it was really an improvement for us.
I'll take care of the transition if you agree. What do you think ?
The text was updated successfully, but these errors were encountered: