Errm, do I seriously have to move to GIT? Ive barely got the hang of using Versions app for SVN. Will it all just work still?
/n00b On Jun 29, 4:34 pm, ch...@doesnthaveone.com wrote: > I agree, I like developing in master and using tags as the primary method for > getting a specific release. If we also want to have a makaanga branch in > between the master / tagging process, that's fine too. > > Also remember that users are encouraged to use the habari/habari repo, which > has system set to check out the latest tag, not master. > > -----Original Message----- > From: "Sean Coates" <s...@seancoates.com> > Sent: Wednesday, June 29, 2011 10:41am > To: habari-dev@googlegroups.com > Subject: Re: [habari-dev] Re: Git-flow > > > Most users just want the latest release. So, if master is equivalent > > to the latest tag, then all they ever have to do is "git pull" to get > > the latest release. If releases just exist in tags, there is an extra > > step to switch to the new tag. > > You can check out a specific branch when cloning with the --branch argument: > > git clone --branch makaangahttps://github.com/habari/habari.git > > (looking up how to spell "makaanga" is certainly an extra step, though (-: ) > > If users are using git and not release tarballs, I'd expect them to know how > to switch branches. > > My preference is to develop in master and branch/tag for releases (and > features). > > S > > -- > To post to this group, send email to habari-dev@googlegroups.com > To unsubscribe from this group, send email to > habari-dev-unsubscr...@googlegroups.com > For more options, visit this group athttp://groups.google.com/group/habari-dev -- To post to this group, send email to habari-dev@googlegroups.com To unsubscribe from this group, send email to habari-dev-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/habari-dev
