Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <beehive-dev@incubator.apache.org>
Received-SPF: pass (hermes.apache.org: domain of richfeit@gmail.com designates
 64.233.162.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding;
        b=VtfrOZ95ruDX4yQECFXF6RguXBxaVkj+nkWHP3LB3cWeQc59+kn3A4QEO0AgGS2WvKJiDN4yfpkeBUIHvDheU1jQN6w013y0tHLV0zFohpu0TBlqxmuO7Fk3TPdqaA2gLSnUYc017tC5KTFbvkpttrsvEBNSDb2Gn/aG1cYZbmM=
Message-ID: <42AF5BB5.6000001@gmail.com>
Date: Tue, 14 Jun 2005 16:35:33 -0600
From: Rich Feit <richfeit@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Beehive Developers <beehive-dev@incubator.apache.org>
Subject: Re: tags versus branches for releases
References: <55c19420050614143128fab10f@mail.gmail.com>
 <e9ac8354050614144271ad8bfb@mail.gmail.com>
In-Reply-To: <e9ac8354050614144271ad8bfb@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I personally would get a warm fuzzy from something like this:

    https://svn.apache.org/repos/asf/incubator/beehive/tags/...

But... how about we wait to see if anyone ever asks for this (or appears 
really confused by us not having it) on beehive-user?

Rich

Eddie ONeil wrote:

>  We can certainly create tags for releases, though in SVN a tag and a
>branch are the same thing.  See:
>
>    http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-4-sect-6
>
>So, the beehive/branches/v1/m1 is going to be exactly the same as
>beehive/tags/v1/m1 except that the former (at least today) will have a
>few additional documentation changes since this is where the doc is
>published for the v1m1 release -- Steve tends to fix a few doc issues
>after we release.
>
>Any code changes that go into either are disallowed and will be backed out.
>
>Thus, it's a different name for the same thing, but if there's demand
>for tags, it's easy enough to create them.
>
>Eddie
>
>
>
>
>On 6/14/05, Jeremiah Johnson <mrtidy@gmail.com> wrote:
>  
>
>>Beehive does not currently use tags in SVN.  This isn't a big issue,
>>but I think that the infrastructure isn't complete without at least
>>discussing it.  I don't think that there is a standard in Apache for
>>tagging a release, so it seems that it is up to the individual
>>projects.
>>
>>As a user of Beehive, it would allow me to sleep better to know that
>>there are tags on each release.  If my well-adopted and impressive
>>applications run into a critical defect, I would know that the source
>>is easily accessible via a tag and a fix could be made without me
>>having to upgrade.
>>
>>Because of SVN's stability in renaming and moving files, it seems that
>>tags offer less value than in other source control systems.  In fact,
>>since SVN doesn't force tags to be read-only, it almost seems that
>>tags provide no value at all.  I can't really identify any value
>>except that I feel better with tags.
>>
>>I see that other projects in Apache (i.e. Axis 2, Geronimo, and
>>MyFaces) use tags - so maybe Beehive should just do as they do :)
>>Maybe this is a reason to tag.
>>
>>I suggest that http://wiki.apache.org/beehive/Release_Process#head-7c5508c82f9623d14b315dac319c53425915e244
>>be updated to be more explicit about branching (as happened in v1m1)
>>and then creating a tag from the branch after a successful vote
>>(didn't happen in v1m1).
>>
>>- jeremiah
>>
>>    
>>
>
>  
>