Clarifying structure modification in HACKING was Re: Suppress display of sensitive info by servers (proposal)

--On Wednesday, April 13, 2005 2:47 PM -0400 Garrett Rooney
<rooneg@electricjellyfish.net> wrote:

> I still think it's technically a violation of the policy, but considering
> the difficulty of actually reving that structure and the fact that anyone

My interpretation of HACKING and APR's versioning policy is different than
yours then. ;-)

So, to make this clearer, would there be any opposition to adding a clause
like this to HACKING under compatibility guidelines:

---
Structure Modifications
Publicly exposed structures (i.e. svn_<type>_t) where a defined constructor 
is available (i.e. svn_<type>_create) may only be modified in the same 
MAJOR line by adding fields to the end of structure.  No modifications to a 
public structure may be adopted in MAJOR.MINOR line.
Private (opaque) structures may be modified at any time.
---
Rewords welcome.  =)
Right now, I think this is implied.  But, that's probably because we've 
adopted this policy implicitly in APR.  Thoughts?  -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org