Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of scheu@us.ibm.com designates
 32.97.110.153 as permitted sender)
In-Reply-To: <46955389.5020503@thoughtcraft.com>
Subject: Re: [Axis2] JAXWS, Axis2 1.3, and RC2 on 7/13
To: axis-dev@ws.apache.org
Cc: axis-dev@ws.apache.org
Message-ID: 
 <OF9C04F400.DC3DAABE-ON87257315.007995B4-86257315.007A20BC@us.ibm.com>
From: R J Scheuerle Jr <scheu@us.ibm.com>
Date: Wed, 11 Jul 2007 17:16:46 -0500
MIME-Version: 1.0
Content-type: multipart/alternative;
	Boundary="0__=08BBF986DFEA13248f9e8a93df938690918c08BBF986DFEA1324"
Content-Disposition: inline

--0__=08BBF986DFEA13248f9e8a93df938690918c08BBF986DFEA1324
Content-type: text/plain; charset=US-ASCII


Rich Scheuerle
IBM Web Services
Apache Axis2 (scheu@apache.org)
512-838-5115  (IBM TL 678-5115)

Glen Daniels <glen@thoughtcraft.com> wrote on 07/11/2007 05:02:49 PM:

> Davanum Srinivas wrote:
> > Does it matter what date *exactly* the branch gets cut? either way we
> > need to make sure that you have some place to work. Would it be
> > suffice to say, we should cut the branch when we cut RC2 and that at
> > any point of time, there will be somewhere where the work can go on?

Agreed.

>
> Broader question - I apologize if I missed something, but what is the
> big deal about the branch?  As per the release process guidelines we
> voted on months ago, changes (in general) happen on the trunk and get
> merged over to the branch.  So if you're waiting for a branch to have a
> "safe place to work and not disturb the trunk" or something like that (I
> don't mean to presume anything, I really just don't know what's going
> on), that doesn't sound right.

>
> If you want a branch to do experimental work on, that is NOT the purpose
> of a release branch - cut your own whenever you please.  If you've got
> stuff which needs to go in to 1.3, and it doesn't break the build, check
> it in! :)  If you are making serious changes that affect architecture or
> APIs, please post diffs and/or a pre-commit discussion thread so we can
> vet them... and THEN check them(*) in! :)

Hi Glen,

We are not working on anything experimental or controversial.  All of our
changes
(at this point) are to push JAX-WS towards CTS compliance.  The changes
outside of jaxws and metadata modules
are (IMHO) minor changes and bug fixes.  We are not changing APIS.  We
would like to get all of this work
into RC2...but we don't want to hold up RC2 for our changes.  Having a
branch when RC2 is cut is only necessary so
that we can continue work and have these fixes for the 7/20 (per Matt's
note).

>
> Yes/no/maybe?
>
> Thanks,
> --Glen
>
> * or modified versions as a result of conversation/consensus.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
--0__=08BBF986DFEA13248f9e8a93df938690918c08BBF986DFEA1324
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline

<html><body>
<p>Rich Scheuerle<br>
IBM Web Services<br>
Apache Axis2 (scheu@apache.org)<br>
512-838-5115  (IBM TL 678-5115)<br>
<br>
<tt>Glen Daniels &lt;glen@thoughtcraft.com&gt; wrote on 07/11/2007 05:02:49 PM:<br>
<br>
&gt; Davanum Srinivas wrote:<br>
&gt; &gt; Does it matter what date *exactly* the branch gets cut? either way we<br>
&gt; &gt; need to make sure that you have some place to work. Would it be<br>
&gt; &gt; suffice to say, we should cut the branch when we cut RC2 and that at<br>
&gt; &gt; any point of time, there will be somewhere where the work can go on?</tt><br>
<br>
<tt>Agreed.</tt><br>
<tt><br>
&gt; <br>
&gt; Broader question - I apologize if I missed something, but what is the <br>
&gt; big deal about the branch? &nbsp;As per the release process guidelines we <br>
&gt; voted on months ago, changes (in general) happen on the trunk and get <br>
&gt; merged over to the branch. &nbsp;So if you're waiting for a branch to have a <br>
&gt; &quot;safe place to work and not disturb the trunk&quot; or something like that (I <br>
&gt; don't mean to presume anything, I really just don't know what's going <br>
&gt; on), that doesn't sound right.</tt><br>
<tt><br>
&gt; <br>
&gt; If you want a branch to do experimental work on, that is NOT the purpose <br>
&gt; of a release branch - cut your own whenever you please. &nbsp;If you've got <br>
&gt; stuff which needs to go in to 1.3, and it doesn't break the build, check <br>
&gt; it in! :) &nbsp;If you are making serious changes that affect architecture or <br>
&gt; APIs, please post diffs and/or a pre-commit discussion thread so we can <br>
&gt; vet them... and THEN check them(*) in! :)</tt><br>
<br>
<tt>Hi Glen,</tt><br>
<br>
<tt>We are not working on anything experimental or controversial. &nbsp;All of our changes</tt><br>
<tt>(at this point) are to push JAX-WS towards CTS compliance. &nbsp;The changes outside of jaxws and metadata modules</tt><br>
<tt>are (IMHO) minor changes and bug fixes. &nbsp;We are not changing APIS. &nbsp;We would like to get all of this work &nbsp;</tt><br>
<tt>into RC2...but we don't want to hold up RC2 for our changes. &nbsp;Having a branch when RC2 is cut is only necessary so </tt><br>
<tt>that we can continue work and have these fixes for the 7/20 (per Matt's note).</tt><br>
<tt><br>
&gt; <br>
&gt; Yes/no/maybe?<br>
&gt; <br>
&gt; Thanks,<br>
&gt; --Glen<br>
&gt; <br>
&gt; * or modified versions as a result of conversation/consensus.<br>
&gt; <br>
&gt; ---------------------------------------------------------------------<br>
&gt; To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org<br>
&gt; For additional commands, e-mail: axis-dev-help@ws.apache.org<br>
&gt; <br>
</tt></body></html>
--0__=08BBF986DFEA13248f9e8a93df938690918c08BBF986DFEA1324--