David Cargill <[EMAIL PROTECTED]> writes:

> I would like to have a vote on adopting the release policy and coding
> conventions attached in the forwarded note below.

Hi David,

Looks good. 

+1

When shipping a release that goes from x.x.x => x.y.z it would be
helpful to list the changes that broke binary compatibility. Sometimes
wrapping Xerces-C to produce Xerces-P is automatic but at othertimes,
it is very helpful to have a list of what changed in the API.

Cheers,
jas.


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

Reply via email to