unity-dev team mailing list archive

[Mark Shuttleworth <mark@xxxxxxxxxx>]

On 01/07/2013 02:09 PM, Ted Gould wrote:
> The problem is that we're not talking about released versions, which
> certainly should manage their API/ABI with proper SO numbers etc,
> we're talking about development trunk.  We've removed the ability to
> have a playground before committing to an API that developers are
> committing to.  We can't expect merging to trunk to be a long term
> commitment to API or ABI stability.  Doing a release is saying "this
> is baked" and we'll commit to it, proposing a merge is not.

Hacking APIs ad-hoc is a recipe for changes release-to-release that feel
uncoordinated, unplanned, badly designed and frustrating. If we are not
conscious and deliberate about small changes, how can we possibly be
conscious, deliberate and designed at a macro release-to-release level?

Mark

Attachment: signature.asc
Description: OpenPGP digital signature