Lionel Dyck <lbd...@gmail.com> writes: Hi Lionel,
> We are having a discussion about best practices with Git. Specifically > in the area of when a project reaches a milestone – say Version 2.0 – > should we just tag that level and leave it at that, should we create a > branch for it, In essence, you should somehow remember the commit which exactly corresponds to that release. You can write down the SHA to a sheet of paper but making a tag is definitely the usual way to do that. Making a branch is useful as well in case you want to develop towards the next milestone in master but do bugfix versions 2.1, 2.2 separately. But creating that branch can be done later if needed as long as you know the commit leading to the release. That would be git branch version-2.0 release-2.0 in case release-2.0 is the tag for the release commit. > or should we make a copy outside of Git for those files so that we can > easily access them for packaging, distribution, reference? IMHO, "git checkout release-2.0" is just as easy (and easlily doable by build servers like jenkins) as looking up the release version at some other location. Bye, Tassilo -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/87eew5ggme.fsf%40gnu.org.
