Thanks David,
+1.
Alberto
At 10.26 20/09/2004 -0400, David Cargill wrote:
Hi Alberto, I will change the following, from:
- x.x.x to x.y.z: the API is source code compatible but not binary compatible (a recompilation of an application using Xerces-C++ should work).
to
- x.x.x to x.y.z: the API is source code compatible but not binary compatible (a recompilation of an application that uses the public headers of Xerces-C++ should work).
If that sounds okay, can I get a +1. Thanks.
Regards, David A. Cargill XML Parser Development IBM Toronto Lab (905) 413-2371, tie 969 [EMAIL PROTECTED]
Alberto Massari <[EMAIL PROTECTED] s.com> To [EMAIL PROTECTED] 09/15/2004 03:42 cc PM Subject Re: [VOTE]: Xerces-C Release Policy Please respond to & Coding Conventions xerces-c-dev
David, I would change the "x.x.x to x.y.z" part to state that the section only refers to the public headers (the ones that gets copied in the include directory and packaged in a binary distribution). This means that client applications that need a source distribution to build will have to expect changes even in the public methods of classes defined in folders like dom\impl.
Alberto
At 13.55 15/09/2004 -0400, David Cargill wrote:
>Hi Xerces-C Committers, >I would like to have a vote on adopting the release policy and coding >conventions attached in the forwarded note below. > >+1 > >Regards, >David A. Cargill >XML Parser Development >IBM Toronto Lab >(905) 413-2371, tie 969 >[EMAIL PROTECTED] >----- Forwarded by David Cargill/Toronto/IBM on 09/15/2004 01:52 PM ----- > > David > Cargill/Toronto/I > BM To > [EMAIL PROTECTED] > 09/02/2004 04:21 cc > PM > Subject > Fw: Xerces-C Release Policy & > Coding Conventions > > > > > > > > > > >Hi, >Earlier this year (Feb 9th to be precise) Alberto posted the "informal" >release policy for Xerces-C ( >http://marc.theaimsgroup.com/?l=xerces-c-dev&m=107632550720436&w=2). I >have taken this information and created a new faq-contributing.xml file to >be included in the doc directory. I also included a section on Coding >Conventions in this file to describe what I think are the main coding >conventions being used in Xerces-C. > >Here is the html version of the file (after running createDocs.bat): > > (See attached file: faq-contributing.html) > > > >I welcome feedback on the release policies and coding conventions. > >Committers: I am hoping to be able to include this file in the Xerces-C 2.6 >GA later this month. So in a few weeks I will request a vote on adopting >the release policies and coding conventions. Thanks. > >Regards, >David A. Cargill >XML Parser Development >IBM Toronto Lab >(905) 413-2371, tie 969 >[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]
--------------------------------------------------------------------- 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]
