> Alan Manuel Gloria: > > stable - latest stable branch, including bugfixes, so 0.3, 0.3.1 etc. > > unstable - latest development branch > > r0.3 - tag for release 0.3 (or v0.3 if you prefer "version")
I incoherently replied: > I don't know about those names, but I agree that we need those 3 branches. Even though you didn't list 3 branches. Ugh. I think I need to go to sleep :-). Anyway, my point is that we should look briefly at others' conventions. This is a small project, I'd like it to be *obvious* to other people what we're doing. And if it's clear to others, we can probably keep track too :-). Relevant pages Google found include: * git's old approach, described in http://git-scm.com/book/en/Distributed-Git-Maintaining-a-Project * http://nvie.com/posts/a-successful-git-branching-model/ * http://skoch.github.com/Git-Workflow/ * http://www.slideshare.net/shuky.dvir/git-workflow-with-gitflow * git's newer approach: http://code.google.com/p/mdanalysis/wiki/DevelopmentWorkflow --- David A. Wheeler ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
