[Gluster-devel] could the rc releases be tagged in git?

[Amar Tumballi]

for those who didn't knew how to get the release-2.0 branch from master
branch in git, below are the instructions.

**sh$ git <http://git-scm.com/download> clone git://
git.sv.gnu.org/gluster.git glusterfs
sh$ cd gluster.git
sh$ git checkout -b release-2.0 origin/release-2.0 #(run only first time)
sh$ git pull
*
*-Amar

On Mon, Jul 6, 2009 at 4:53 PM, Anand Avati <avati at gluster.com> wrote:

> > Could the rc/qa releases be tagged in git? It'd be helpful to know
> > what fixes to expect in a given point release. Also, is there an
> > intention to eventually merge the release-2.0 branch with master, or
> > is the master branch going to eventually become 2.1?
>
> release-2.0 will just keep getting bug fixes, and is the recommended
> branch for usage (till release-2.1 branch is made down the line).
> Minor releases (2.0.x) will be made off the release-2.0 branch.
> Patches going into release-2.0 (bug fixes) get double committed into
> mainline, but mainline gets other patches as well and is more dynamic,
> hence not recommended for deployments. 2.1 branch will eventually be
> made off the mainline.
>
> Avati
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>
>


-- 
Regards,
Amar Tumballi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20090706/89c4d0a0/attachment-0003.html>