Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 20920 invoked from network); 14 Sep 2006 21:34:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Sep 2006 21:34:02 -0000 Received: (qmail 72541 invoked by uid 500); 14 Sep 2006 21:33:59 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 72505 invoked by uid 500); 14 Sep 2006 21:33:59 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 72494 invoked by uid 99); 14 Sep 2006 21:33:59 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Sep 2006 14:33:59 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=ajith.ranabahu@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=DNS_FROM_RFC_ABUSE,HTML_60_70,HTML_MESSAGE,HTML_TAG_EXIST_TBODY,RCVD_BY_IP DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from ([64.233.182.184:11769] helo=nf-out-0910.google.com) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id B2/90-07618-87AC9054 for ; Thu, 14 Sep 2006 14:33:55 -0700 Received: by nf-out-0910.google.com with SMTP id x29so1969904nfb for ; Thu, 14 Sep 2006 14:32:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=FNYTkHGIK9w87dsgBd5Ub1jHjuTFdP8q9FGq58J9nh2Z7jkKyo66z9nhyxGH0g08fJnmw1e3qhO9VUjFR9E5Q9ibrFZQEuKhrUuGJHVhKhRBprl31GvgCM68PF8jIHjsVPP1C5FDrQy7o0eicsXaBlS1JGxcUuW3Qgw2fxZnSk4= Received: by 10.48.162.15 with SMTP id k15mr12605498nfe; Thu, 14 Sep 2006 14:32:37 -0700 (PDT) Received: by 10.48.163.5 with HTTP; Thu, 14 Sep 2006 14:32:37 -0700 (PDT) Message-ID: Date: Thu, 14 Sep 2006 17:32:37 -0400 From: "Ajith Ranabahu" To: axis-dev@ws.apache.org Subject: Re: [Axis2][Vote] Create a branch for the Axis2 1.1 release In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_53244_10196031.1158269557255" References: X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_53244_10196031.1158269557255 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Nick, Yep, That is definitely a reason to do so. What I'm a bit worried about is that when you do a branch then whatever the bug fixes you do to the branch would also need to go to the trunk. And believe me, there is going to be a significant number of bug fixes before the release :) So I guess the best time to do the branch would be just after the code freeze, so that the folks who want to work on the code can keep on working with it without effecting the release. Ajith On 9/14/06, Nicholas L Gallardo wrote: > > > Ajith, > > Branching before would allow others to continue longer term development > items while the final fixes are being applied to the upcoming release. > > Regards, > > > Nicholas Gallardo > WebSphere - WebServices Development > nlgallar@us.ibm.com > Phone: 512-838-1182 > Building: 901 / 5G-016 > > > *"Ajith Ranabahu" * > > 09/14/2006 04:11 PM > Please respond to > axis-dev@ws.apache.org > > To > axis-dev@ws.apache.org cc > > Subject > Re: [Axis2][Vote] Create a branch for the Axis2 1.1 release > > > > > > > Hi guys, > If I understand right the branching usually happens at the same time of a > release (or slightly after) and is usually used to fix issues in that > particular release. We can definitely use a branch before the release but is > there any particular reason why we need a branch before the release ? > > > -- > Ajith Ranabahu > -- Ajith Ranabahu ------=_Part_53244_10196031.1158269557255 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Nick,
Yep, That is definitely a reason to do so. What I'm a bit worried about is that when you do a branch then whatever the bug fixes you do to the branch would also need to go to the trunk. And believe me, there is going to be a significant number of bug fixes before the release :) So I guess the best time to do the branch would be just after the code freeze, so that the folks who want to work on the code can keep on working with it without effecting the release.

Ajith

On 9/14/06, Nicholas L Gallardo <nlgallar@us.ibm.com> wrote:

Ajith,

Branching before would allow others to continue longer term development items while the final fixes are being applied to the upcoming release.

Regards,


Nicholas Gallardo
WebSphere  -  WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016


"Ajith Ranabahu" <ajith.ranabahu@gmail.com>

09/14/2006 04:11 PM

Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2][Vote] Create a branch for the Axis2 1.1 release







Hi guys,
If I understand right the branching usually happens at the same time  of a release (or slightly after) and is usually used to fix issues in that particular release. We can definitely use a branch before the release but is there any particular reason why we need a branch before the release ?


--
Ajith Ranabahu



--
Ajith Ranabahu ------=_Part_53244_10196031.1158269557255--