Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D04EC11C9E for ; Tue, 22 Jul 2014 17:06:06 +0000 (UTC) Received: (qmail 62658 invoked by uid 500); 22 Jul 2014 17:06:06 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 62607 invoked by uid 500); 22 Jul 2014 17:06:06 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 62597 invoked by uid 99); 22 Jul 2014 17:06:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jul 2014 17:06:06 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of raminderjsingh@gmail.com designates 209.85.216.47 as permitted sender) Received: from [209.85.216.47] (HELO mail-qa0-f47.google.com) (209.85.216.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jul 2014 17:06:00 +0000 Received: by mail-qa0-f47.google.com with SMTP id i13so6983561qae.34 for ; Tue, 22 Jul 2014 10:05:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=amDy0/8ZuTyEua98K72NGTG/vmAnYCuLO/8nqfo3jSw=; b=cQHbnQEXDuUN7G8JDOjsWKW5HipT/lesTOWssVf2VTNYikR2ZrjbjemxWYniIJOpfo 9P8pv6EKNs3FLQ1VSQnGlcrjj4Dd86D3PMAdQDuXc1mjaNUJnd4ki9Dwp8PhOJGMfSEd yDEFzaJqtWQfI5zvK/CGSI1tLz6v7x+tF23p1LGYn9JEyWON2ys10vaOcPPZ5D9v/D0t aqIJfKp2AlHov+kLTHHwvENVUTqWGq71F85Tr6ekZ02i9F0bC8DKDHupVdbmJNHGPKkQ pBy0V85FJPgObzRYug7wGTYRtgSbfyC9KLbK0D7geLP3bodvtYOuCQkoLo+qvYxFCjsk ZGqQ== MIME-Version: 1.0 X-Received: by 10.224.34.73 with SMTP id k9mr58121655qad.11.1406048739952; Tue, 22 Jul 2014 10:05:39 -0700 (PDT) Received: by 10.140.16.193 with HTTP; Tue, 22 Jul 2014 10:05:39 -0700 (PDT) In-Reply-To: <776B2DEB-BF8B-43CD-A74F-952F0DB979EA@apache.org> References: <776B2DEB-BF8B-43CD-A74F-952F0DB979EA@apache.org> Date: Tue, 22 Jul 2014 13:05:39 -0400 Message-ID: Subject: Re: [DISCUSS] delete dead branches From: Raminderjeet Singh To: dev@airavata.apache.org Content-Type: multipart/alternative; boundary=001a11c2047cae8fe804fecb3beb X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2047cae8fe804fecb3beb Content-Type: text/plain; charset=UTF-8 I created 0.11-JGlobus2.1-rc to evaluate airavata to use jglobus 2.1 version and also integrate unicore provider. Its a working branch for Jglobus 2.1 and Unicore provider. I think we should leave this until we have unicore provider working in trunk. Thanks Raminder On Tue, Jul 22, 2014 at 12:03 PM, Suresh Marru wrote: > Hi All, > > As a good practice to keep our source tree clean, how about we remove all > non-active branches? We should leave all the tags for reference, but it > might be a good idea to not have branches where there is no active > development nor we are supporting them. > > After we move to semantic versioning (beyond 1.0), if a version of > Airavata is being used in production, we should make periodic releases from > that branch with a minor increment. But otherwise we should either support > or abandon branches. Tags are forever immutable references. > > Thoughts? > > If we have a consensus, I suggest deleting the following branches: > 0.1-incubating > 0.2-incubating > 0.3-incubating-snapshot > 0.4-incubating > 0.5 > airavata-0.7 > airavata-0.8-maintenance-branch > temp > > I am unsure of 0.11-JGlobus2.1-rc branch (unless some one can confirm > deletion of this, I will leave this one alone). > > Suresh --001a11c2047cae8fe804fecb3beb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I created 0.11-JGlobus2.1-rc to evaluate airavata to use = jglobus 2.1 version and also integrate unicore provider. Its a working bran= ch for Jglobus 2.1 and Unicore provider. I think we should leave this until= we have unicore provider working in trunk.=C2=A0

Thanks
Raminder


On Tue,= Jul 22, 2014 at 12:03 PM, Suresh Marru <smarru@apache.org> = wrote:
Hi All,

As a good practice to keep our source tree clean, how about we remove all n= on-active branches? We should leave all the tags for reference, but it migh= t be a good idea to not have branches where there is no active development = nor we are supporting them.

After we move to semantic versioning (beyond 1.0), if a version of Airavata= is being used in production, we should make periodic releases from that br= anch with a minor increment. But otherwise we should either support or aban= don branches. Tags are forever immutable references.

Thoughts?

If we have a consensus, I suggest deleting the following branches:
0.1-incubating
0.2-incubating
0.3-incubating-snapshot
0.4-incubating
0.5
airavata-0.7
airavata-0.8-maintenance-branch
temp

I am unsure of 0.11-JGlobus2.1-rc =C2=A0branch (unless some one can confirm= deletion of this, I will leave this one alone).

Suresh

--001a11c2047cae8fe804fecb3beb--