Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem

From: Gaudenz Steinlin <gaudenz@soziologie.ch>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Date: Wed, 01 Dec 2010 09:37:58 +0100	[thread overview]
Message-ID: <1291192005-sup-7698@meteor.durcheinandertal.local> (raw)
In-Reply-To: <1291097850-sup-6043@tilus.net>

[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]

Excerpts from Tero Tilus's message of Die Nov 30 07:22:48 +0100 2010:
> Gaudenz Steinlin, 2010-11-29 11:41:
> > As far as I understood the branch layout the flow of changes is
> > master -> next -> release. So applying to next would mean it ends up
> > in the next release (0.12).
> 
> Master is considered "stable" and next "unstable".  Releases are
> tagged from master and small changes may go directly to master.  New
> features are introduced in next and merged to master when they are
> considered stable (enough).

Thanks for clarifying this.At the moment this does not seem to reflect
the current reality in the git repository. Master has quite a lot of
commits next does not have. Also next has not been updated since
several months.

I guess this is due to the fact that there were no major code changes
during the last months and therefore all the work has been done
directly on master. 

Gaudenz
-- 
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 0 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel