On Fri, Oct 1, 2010 at 1:53 AM, Jody Garnett
<jody.garnett@xxxxxxxxx> wrote:
Thanks Jesse!
Link for others is here: http://udig.refractions.net/confluence/display/ADMIN/Making+a+Formal+Release
Jesse when we release 1.2.1 we should update this example to be udig specific; I assume we are going to name our tags with a version number and so forth? Are their any git specific conventions we need to be aware of?
There are no conventions that I am aware of. We can tag anything we want, but perhaps we can create tags of the form:
Release/1.2.1-RC1
I have been thinking about it and I think we should have an associated branch on the public repository for each release line.
For example I can see having:
master
1.2.x
2.0.x
1.2.x would have several tags and possibly we can even consider sub-branches (although for now lets avoid them)
Also as I read the IRC log; and these instructions; I would like to write down on the names used for the remote repositories (even just in the documentation) so we can keep the examples straight. I have been using "udig" to indicate the main repository; and "origin" to refer to my clone.
I think using "origin" in documentation is dangerous since it has special meaning in git. Perhaps main udig(m-udig), clone-udig (c-udig) and local udig (l-udig)
is that ok?
Jesse
