Clarify Git branches

[Jackbennett]

Hello, We should agree something acceptable here and then;

• Update README Current development builds a callout to contributing
• Update CONTRIBUTING.md with the clarifications from this issue
• Add a callout to CONTRIBUTING.md on cmder.net too (something small).

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.

1. Master holds the latest acceptable changes
2. Keep master passing successful builds
3. Releases are tested and then tagged by a human
4. Any other branch can be for major changes somebody might want. But mainly work stays on master.

Concerns

• As I understand our tests pretty much consist of only cmder compiling so that could use some work.

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.

[Stanzilla]

I am fine with dropping development I've been ignoring it for ages anyway :D Apart from that, a nice CONTRIBUTING.md would be good to have, indeed. Other than that, feature branches are fine and the norm, just don't forget to delete them when your PR gets merged.

[DRSDavidSoft]

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 development, and sticking to the CONTRIBUTING.md's guide. Best practice to avoid confusion for newcomers like me!

[MartiUK]

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.

[Stanzilla]

@MartiUK I think you are the only person with enough permissions to delete it btw

[daxgames]

@cmderdev/core @cmderdev/trusted-contributors Can we close this?