incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Frishberg <>
Subject Re: Component creation workflow
Date Tue, 28 Feb 2012 21:53:36 GMT
I find that approach a little bit too gun-slinger in the wild-west.  If
this was just an application, I wouldn't see as much of a point for
component specification.  However, this is an SDK.  More developers are
interested in our component specifications than just those who want to
check out the apache code.  We have strong backwards-compatibility
requirements, and having a wiki where the API proposal is clearly laid out
with possible issues makes sense to me.  Of course one of the main reasons
I favor this approach is just that personally I find it extremely hard to
follow the discussions on an email thread.

Just my two cents,

On Tue, Feb 28, 2012 at 2:44 PM, Michael A. Labriola <> wrote:

> >Specs were useful as a mechanism to foster communication and coordination
> between several separate teams of QA, Doc, and management, and/or between
> several engineers working together in a coordinated fashion, but I >think
> it will be the exception that more than one engineer will be working like
> that.
> +1

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message