Hi James,
I have on objections (ie. +1).

I was thinking that July also sounds like a good time to put out a Xercesc
2.7 release...  I will request a vote for it in July (after my vacation)...

Regards,
David A. Cargill
XML Parser Development
IBM Toronto Lab
(905) 413-2371, tie 969
[EMAIL PROTECTED]


                                                                           
             James Berry                                                   
             <[EMAIL PROTECTED]                                             
             g>                                                         To 
                                       [email protected]             
             06/14/2005 10:46                                           cc 
             PM                                                            
                                                                   Subject 
                                       Re: 3.0 unstable branch update      
             Please respond to         (Merge now?)                        
                   c-dev                                                   
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




I heard an opinion from Alberto, but not from anybody else, I
believe. I'm planning to do the merge on Wednesday evening (US) or
Thursday sometime.

Please let me know if you have objections to this.

Note that once I merge, 3.0 (trunk head) and 2.7 will truly be
distinct creatures. I've been shadowing commits to the 2.7 branch for
practice, even though it's still basically equivalent to trunk. But
anyway, if you intend something to go both to head and 2.7 you'll
want to merge it over.

James.

On Jun 13, 2005, at 5:51 PM, James Berry wrote:

> Here I am again with my weekly check-in and query about the state
> of the 3.0 unstable branch.
>
> I've got the rest of this week in town before I'm out through mid-
> July. Do to that schedule, I want to see if we can get the 3.0
> unstable branch merged to trunk during the next couple of days, in
> order that it doesn't diverge too much from trunk, and so that I
> can help with any issues that come up before I leave.
>
> Thanks to all of you, the 3.0 unstable branch is now more stable,
> though I'm sure there's still work to do. In particular Dave,
> Alberto, Axel, and Greg have all contributed bug reports and
> platform-specific fixes. Here's an update to the platform support
> (your feedback and corrections welcome):
>
> Configure/Build success:
>
>     - Mac OS X 10.4    jberry (command line build, not XCode)
>     - FreeBSD 4.11      jberry (minotaur.apache.org)
>     - Mingw ver?           amassari
>     - cygwin                   Axel
>     - SuSE Linux 9.3    Axel (gcc version 3.3.5 20050117
> (prerelease) (SUSE Linux), GNU Make 3.80)
>     - Solaris (ver?)        Greg Franks (Sunpro compiler)
>     - Solaris                   dbertoni (GCC -- with notes?)
>     - Windows VS.net  amassari
>
> The following are unknown, by me anyway:
>
>     - AIX                        (issues, according to dave)
>     - Unix Services for Windows (is that what it's called?)
>     - NetBSD
>     - OpenBSD
>     - True64
>
> Since we're building on many more platforms now, I propose that we
> now merge to trunk. My intent was not that we do all development on
> my temporary 3.0-unstable branch, but that we use it to get the
> thing buildable for many of our developers.
>
> Furthermore, I'd like to hold off making any major non-build-
> related changes on the unstable branch, so that it doesn't diverge
> too much from trunk.
>
> So my proposal in short form:
>
>     - Merge 3.0 unstable to trunk, with your consensus, over the
> next couple of days.
>     - Concentrate effort to fix any remaining non-building platform
> that is critical to developer progress.
>     - Perform remainder of work for Xerces 3.0 on the main trunk.
>
> Feedback?
>
> James.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to