Mailing-List: contact general-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@xml.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Date: Thu, 14 Oct 2004 17:23:26 +0530
From: Neeraj Bajaj <Neeraj.Bajaj@Sun.COM>
Subject: Re: Donation of JAXP 1.3 Sources to Apache
To: xerces-j-user@xml.apache.org
Cc: general@xml.apache.org, commons-dev@xml.apache.org,
        Eduardo Pelegri-Llopart <Eduardo.Pelegrillopart@Sun.COM>,
        Jeff Suttor <Jeff.Suttor@Sun.COM>, Suresh.K@Sun.COM,
        xerces-j-dev@xml.apache.org, xalan-dev@xml.apache.org
Reply-to: Neeraj.Bajaj@Sun.COM
Message-id: <416E68B6.1070004@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_FMzVoAW5Cv2ScBEFU4LEHw)"
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
 Gecko/20030208 Netscape/7.02 (VAUSSU03)
References: 
 <OF4C007B98.0AAF149C-ON85256F2C.00673775-85256F2C.00698CC0@ca.ibm.com>

--Boundary_(ID_FMzVoAW5Cv2ScBEFU4LEHw)
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT


Michael Glavassevich wrote:

>Neeraj Bajaj <Neeraj.Bajaj@sun.com> wrote on 10/13/2004 10:11:00 AM:
>
>  
>
>>Hello All,
>>
>>I was wondering when can we start merging the JAXP 1.3 sources ? Merging 
>>    
>>
>
>  
>
>>the code in branch/review/testing/committing to main trunk
>>would take time so at least from my side i would like to see this work 
>>started as early as possible say from tomorrow.
>>
>>What is the general procedure ? Is there any formality that needs to be 
>>completed first ? What is the opinion of
>>(Xml-commons/Xerces/Xalan) committers ?
>>    
>>
>
>I'm interested in getting started on this so tomorrow sounds good to me. 
>Formally, that's a +1 from me.
>
It would be good to see response from Xalan committers too.  

> 
>  
>
>>As the sources would be put in a branch so it won't affect normal 
>>development but it would be good if we can restrict
>>large chunk of changes to the main trunk and fix only critical changes. 
>>It would help merging the changes back to main
>>trunk. What do others think ?
>>    
>>
>
>I think that's a good idea. We should merge the RI code into the main 
>trunk in stages. One of the first things I'd like to see on the Xerces 
>main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up 
>the hacks currently there for SAX 2.0.2 and DOM Level 3.
>  
>
I agree.

Thanks,
Neeraj


--Boundary_(ID_FMzVoAW5Cv2ScBEFU4LEHw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
<br>
<br>
Michael Glavassevich wrote:<br>
<blockquote type="cite"
 cite="midOF4C007B98.0AAF149C-ON85256F2C.00673775-85256F2C.00698CC0@ca.ibm.com">
  <pre wrap="">Neeraj Bajaj <a class="moz-txt-link-rfc2396E" href="mailto:Neeraj.Bajaj@sun.com">&lt;Neeraj.Bajaj@sun.com&gt;</a> wrote on 10/13/2004 10:11:00 AM:

  </pre>
  <blockquote type="cite">
    <pre wrap="">Hello All,

I was wondering when can we start merging the JAXP 1.3 sources ? Merging 
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">the code in branch/review/testing/committing to main trunk
would take time so at least from my side i would like to see this work 
started as early as possible say from tomorrow.

What is the general procedure ? Is there any formality that needs to be 
completed first ? What is the opinion of
(Xml-commons/Xerces/Xalan) committers ?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I'm interested in getting started on this so tomorrow sounds good to me. 
Formally, that's a +1 from me.</pre>
</blockquote>
It would be good to see response from Xalan committers too. &nbsp;<br>
<blockquote type="cite"
 cite="midOF4C007B98.0AAF149C-ON85256F2C.00673775-85256F2C.00698CC0@ca.ibm.com">
  <pre wrap="">
 
  </pre>
  <blockquote type="cite">
    <pre wrap="">As the sources would be put in a branch so it won't affect normal 
development but it would be good if we can restrict
large chunk of changes to the main trunk and fix only critical changes. 
It would help merging the changes back to main
trunk. What do others think ?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I think that's a good idea. We should merge the RI code into the main 
trunk in stages. One of the first things I'd like to see on the Xerces 
main trunk is an update of xml-apis.jar to JAXP 1.3, so we can clean-up 
the hacks currently there for SAX 2.0.2 and DOM Level 3.
  </pre>
</blockquote>
I agree.<br>
<br>
Thanks,<br>
Neeraj<br>
<br>
</body>
</html>

--Boundary_(ID_FMzVoAW5Cv2ScBEFU4LEHw)--