incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carol Frampton <>
Subject Re: SDK Inclusion Process (was re: [OT] What are we doing here?)
Date Tue, 13 Mar 2012 19:28:09 GMT
Alex has said this before but I'll remind people.  I think he/we are
proposing that there be 2 or 3 branches with the final branch being trunk.
 Trunk becomes the next release of the SDK.  So, for example, code could
move from the whiteboard or, or some external source, to the "not quite
polished" branch, for lack of a better name, which would give people a
chance to use it, test it, refine it, etc, and then when it was deemed
"ready" it could be pushed/merged to trunk which would make it part of the
next release.

I think I remember hearing there are several Apache projects that have
this model.


On 3/13/12 1 :54PM, "Alex Harui" <> wrote:

>On 3/13/12 10:42 AM, "Omar Gonzalez" <> wrote:
>> There's an awful lot of process described in your response. This is
>> what I'm saying we need to come to an agreement on, finalize a decision
>> publish this process on the wiki.
>Yes, there is a sequence, but I think it is the same short set of steps in
>iteration.  And, I didn't make this up, I believe other Apache projects
>this way.
>What is hard is trying to remember however many steps that will eventually
>be on that checklist.  What is slow is trying to use that long checklist
>validate promotion or acceptance of a change.
>I want this to be simple:  Use your own good judgment before promoting
>to the next branch with the higher quality bar.  The onus is on you to get
>enough eyes on your stuff before promoting it.  That's what the mailing
>and JIRA are for.  Within a branch or whiteboard, any commit is good as
>as it is an incremental improvement and doesn't appear to break anything.
>I think I can remember that.
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.

View raw message