Moving cairoplot from Launchpad to GitHub - CairoPlot

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Moving cairoplot from Launchpad to GitHub
Received-SPF: pass (google.com: domain of alf.rodr...@gmail.com designates 209.85.215.178 as permitted sender) client-ip=209.85.215.178;
MIME-Version: 1.0
In-Reply-To: <b159fe49-c647-476d-a540-77e89d8806ca@r6g2000yqr.googlegroups.com>
References: <CAFSJ_BVBr_cF64VDXSi6qZeCM-tgD9EwutKSDkUvOuuaZJC...@mail.gmail.com>
	<CADya-sY2UJxFGFd2hwC5iYt-QKpv6nCxfdQTs+nzW5Xmwxd...@mail.gmail.com>
	<CADya-sZ4PY5+BHyjjFSgVS+fjvE8FR5WFZcYgSGG2=puG7G...@mail.gmail.com>
	<A9EAEA47-6EAB-43AD-AB07-5B1BBE05B...@gmail.com>
	<4EE01E78.80...@gmail.com>
	<CADya-saim92Q75ufRNesPgZ03ZPb3Mc9O3EHEHN1xaCY9L=...@mail.gmail.com>
	<b159fe49-c647-476d-a540-77e89d880...@r6g2000yqr.googlegroups.com>
Date: Tue, 13 Dec 2011 18:38:32 -0300
Message-ID: <CAFSJ_BVnGKJWdZTDrhfR+-OgkENEysvxit7Gq7B822aUaNO...@mail.gmail.com>
Subject: Re: [CairoPlot] Re: Moving cairoplot from Launchpad to GitHub
From: =?ISO-8859-1?Q?Rodrigo_Ara=FAjo?= <alf.rodr...@gmail.com>
To: cairoplot@googlegroups.com
Content-Type: multipart/alternative; boundary=000e0ce0423ca13a6404b40012fb

--000e0ce0423ca13a6404b40012fb
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey everyone,

Still on the topic of how to use Git properly, I've been reading the ProGit
ebook[1].
It seems to be a very good way to understand how the tool works and how we
can use it properly. I'm almost getting to the section about tagging.

But I'm surely gonna read Magnun's link.

Best regards,

[1] http://progit.org/book/

On Tue, Dec 13, 2011 at 5:10 PM, Magnun Leno <magnun.l...@gmail.com> wrote:

>
>
> On 8 dez, 02:30, Mike Rooney <mroo...@gmail.com> wrote:
> > On Wed, Dec 7, 2011 at 9:18 PM, Magnun Leno <magnun.l...@gmail.com>
> wrote:
> > > Btw, do any of you know what's the best practice to release a stable
> > > version on GitHub? I guess the right thing to do would be to release
> the
> > > current trunk as version 1.2 and start working on new features.
> >
> > Git does have the concept of tags, but AFAIK you can't commit to them o=
r
> > merge, so using them for releases would make it a pain later if you
> needed
> > to commit a bug fix and release that version with it. Generally at the
> > point at which you want to branch on master, you can just type "git
> branch
> > 1.2" and you'll have created a 1.2 branch, which you can later checkout=
,
> > commit a bugfix to, and merge back to master if necessary.
> >
> > I've seen a bunch of Git projects just have the policy of "build from
> trunk
> > or the latest branches", and another set which upload tarballs/zips for
> > each version to the Downloads section, and either seems to work, though=
 I
> > always feel more confident about released Downloads.
> >
> > Sorry if any of this is redundant or not useful :]
> >
> > - Michael
>
> The good part of using tags and etc, is that GitHub automatically
> generates packages (zip or tar.gz) for it.
>
> Indeed you're correct, you can't commit or merge to a tag. A tag is
> just a marker that we can assign for an specific commit. I've recently
> found this article[1] which explains nicely the basic Git workflow. I
> strongly recommend that everyone read it.
>
> I hope this will help us.
>
> Magnun Leno
> www.mindbending.org
> @mind_bend
>
> [1]: http://nvie.com/posts/a-successful-git-branching-model/
>
> --
> You received this message because you are subscribed to the Google Groups
> "CairoPlot" group.
> To post to this group, send email to cairoplot@googlegroups.com.
> To unsubscribe from this group, send email to
> cairoplot+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/cairoplot?hl=3Den.
>
>


--=20
Rodrigo Ara=FAjo

--000e0ce0423ca13a6404b40012fb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey everyone,<div><br></div><div>Still on the topic of how to use Git prope=
rly, I&#39;ve been reading the ProGit ebook[1].</div><div>It seems to be a =
very good way to understand how the tool works and how we can use it proper=
ly. I&#39;m almost getting to the section about tagging.</div>
<div><br></div><div>But I&#39;m surely gonna read Magnun&#39;s link.</div><=
div><br></div><div>Best regards,</div><div><br></div><div>[1]=A0<a href=3D"=
http://progit.org/book/">http://progit.org/book/</a><br><br><div class=3D"g=
mail_quote">
On Tue, Dec 13, 2011 at 5:10 PM, Magnun Leno <span dir=3D"ltr">&lt;<a href=
=3D"mailto:magnun.l...@gmail.com">magnun.l...@gmail.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<br>
<br>
On 8 dez, 02:30, Mike Rooney &lt;<a href=3D"mailto:mroo...@gmail.com">mroo.=
....@gmail.com</a>&gt; wrote:<br>
<div class=3D"im">&gt; On Wed, Dec 7, 2011 at 9:18 PM, Magnun Leno &lt;<a h=
ref=3D"mailto:magnun.l...@gmail.com">magnun.l...@gmail.com</a>&gt; wrote:<b=
r>
&gt; &gt; Btw, do any of you know what&#39;s the best practice to release a=
 stable<br>
&gt; &gt; version on GitHub? I guess the right thing to do would be to rele=
ase the<br>
&gt; &gt; current trunk as version 1.2 and start working on new features.<b=
r>
&gt;<br>
&gt; Git does have the concept of tags, but AFAIK you can&#39;t commit to t=
hem or<br>
&gt; merge, so using them for releases would make it a pain later if you ne=
eded<br>
&gt; to commit a bug fix and release that version with it. Generally at the=
<br>
&gt; point at which you want to branch on master, you can just type &quot;g=
it branch<br>
&gt; 1.2&quot; and you&#39;ll have created a 1.2 branch, which you can late=
r checkout,<br>
&gt; commit a bugfix to, and merge back to master if necessary.<br>
&gt;<br>
&gt; I&#39;ve seen a bunch of Git projects just have the policy of &quot;bu=
ild from trunk<br>
&gt; or the latest branches&quot;, and another set which upload tarballs/zi=
ps for<br>
&gt; each version to the Downloads section, and either seems to work, thoug=
h I<br>
&gt; always feel more confident about released Downloads.<br>
&gt;<br>
&gt; Sorry if any of this is redundant or not useful :]<br>
&gt;<br>
&gt; - Michael<br>
<br>
</div>The good part of using tags and etc, is that GitHub automatically<br>
generates packages (zip or tar.gz) for it.<br>
<br>
Indeed you&#39;re correct, you can&#39;t commit or merge to a tag. A tag is=
<br>
just a marker that we can assign for an specific commit. I&#39;ve recently<=
br>
found this article[1] which explains nicely the basic Git workflow. I<br>
strongly recommend that everyone read it.<br>
<br>
I hope this will help us.<br>
<br>
Magnun Leno<br>
<a href=3D"http://www.mindbending.org" target=3D"_blank">www.mindbending.or=
g</a><br>
@mind_bend<br>
<br>
[1]: <a href=3D"http://nvie.com/posts/a-successful-git-branching-model/" ta=
rget=3D"_blank">http://nvie.com/posts/a-successful-git-branching-model/</a>=
<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
You received this message because you are subscribed to the Google Groups &=
quot;CairoPlot&quot; group.<br>
To post to this group, send email to <a href=3D"mailto:cairoplot@googlegrou=
ps.com">cairoplot@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href=3D"mailto:cairoplot%2=
Bunsubscribe@googlegroups.com">cairoplot+unsubscribe@googlegroups.com</a>.<=
br>
For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/cairoplot?hl=3Den" target=3D"_blank">http://groups.google.com/group/ca=
iroplot?hl=3Den</a>.<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Rodrigo Ara=FAjo<br><br>
</div>

--000e0ce0423ca13a6404b40012fb--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
