Vote on restructuring the GitHub branches

[cmd644]

Instead of splitting up the branches by front, middle, and backend, let's take a Google style approach, detailed below:

Application Channels: stable, canary, dev

stable: least buggy channel, this is what we would deploy to the web application in "production"

canary: dev type channel with the newest features, this is where we test the features, this is our last chance to actually get the feature nailed down with very little bugs before merging into stable.

dev: most buggy channel with latest features, this is where we dump most of our commits, where we will primarily work. this branch is where we will build out our features.

Let's take a vote on restructuring like this, please add a comment on whether or not we should do it this way. I've given it some thought, and this might be a better way of doing it.

[oliveoil222]

This makes sense as long as we can have some labeling in the branches to keep it organized. I say we do this approach

[jjkagie]

This makes sense to me.

[SamCain04]

I agree, I think this approach is much more efficient.

[dallonjarman]

That works for me!

[hannahpenado]

Sounds good to me!

[dallonjarman]

@cmd644 wanted to check in and see if this is an issue we can resolve

[cmd644]

Yes, we can close it now... forgot to do it... make sure y'all update your forks of the main repo... you'll probably have to use something git pull --all