On Wed, Jan 06, 2010 at 02:47:26PM -0600, Eric Evans wrote: > On Wed, 2010-01-06 at 14:29 -0600, Jonathan Ellis wrote: > > > > One question: do we need a 3-tuple? > > What would be the rules governing that 3rd value?
I usually like the first to be non-compatible changes, the second to be new functionality which is backward compatible and the third to be bugfixes. In the case of the .thrift file the third value might be for adding comments or something like that. > > The 0.5 api is a superset of the 0.4 one in method names and > > arguments, but the exceptions declared are different, so client code > > in compiled languages with checked exceptions (only Java?) probably > > needed some light editing to upgrade. > > That still breaks existing code though. Would you not bump the major for > such a case? I would agree that you should bump the major for this change. Even if some languages would not be affected, its better for people to be alerted. If they know enough not to update their stuff fine, otherwise you'll have fewer issues if people are forced to update. -Anthony -- ------------------------------------------------------------------------ Anthony Molinaro <antho...@alumni.caltech.edu>
