-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Clarify Git branches #1679
Comments
I am fine with dropping |
I like to mention that @MartiUK has already done an awesome job for writing a CONTRIBUTING.md at: cmder/CONTRIBUTING.md. Since it seems that every feature branch has its own name (@daxgames's great practice), I agree with @Stanzilla on dropping |
The majority of outside contributors never followed the "fork and make changes in the development branch" so I'm fine with dropping it. I'd like to find some time into looking into automated GUI testing since I would think it would be more appropriate than just running the included scripts for consistency. |
@MartiUK I think you are the only person with enough permissions to delete it btw |
@cmderdev/core @cmderdev/trusted-contributors Can we close this? |
Hello, We should agree something acceptable here and then;
I'm sure there's various git flows with names we could subscribe to if you want but initially I thought to propose what my understanding was of how things seem to be done lately.
Proposal
Pretty much what we already have it's just not completely clear.
Concerns
In the Past
Initially we always had work and PR's on the development branch. As releases were packaged from master. Since then we've started using git and githubs tags to publish releases. There was always some ambiguity when a change was worth waiting to go through development or just apply onto master.
I pretty much focus on powershell and try to help where I can, I don't think I've ever cut a release so let's hear from @cmderdev/trusted-contributors as well as the community going forward. Related to the stalled #1372.
The text was updated successfully, but these errors were encountered: