Closed basepi closed 13 years ago
Also, I think we should take a leaf out of libgit2's workflow and make the "dev" branch the default branch (you can do that in the admin section of the repo)
I think we've talked about this enough and decided on our workflow (I hope so, since we're well into the project, hehe), so I'm closing this.
I think we should define our workflow. I was reading in Pro Git the other day, as well as thinking about the libgit2 workflow, and I think we should kind of follow something similar. Rather than having branches that are "us"-specific, I think we should have a working "master" branch, a beta/still-needs-testing "development" branch, and then open branches for each issue as we're working on it, or whatever, merging into development as things get stable and deleting those branches.
I dunno, maybe we'll just have our own branches, but I think having at least master and dev branches would be good for the workflow, since we're going to continue developing this app after school's over.
Your thoughts?