On 10/2/12 5:43 AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote:
> Yeah, that was for people saying I didn't do my homework. :)
>
> I'm just a bit confused as to what and where I am committing things
> with the patches branch there. It doesn't seem like people are
> committing to trunk.
Hopefully you have signed up for flex-commits mailing list. You will see
that almost all activity is in the "develop" branch.
>
> I'm not exactly understanding the mustella tests and "when you have to
> write a test". As well as committing something and making sure tests
> don't break. I have not run the tests and it dosn't look that simple
> to run.
There is no "qa" team any more so we are going to have to rely on
Test-Driven Development. That generally means that new/changed code should
be accompanied by tests, either in Mustella or FlexUnit. There is a
Mustella Overview on the wiki, and we are open to feedback on how to make it
better.
>
> Maybe someday a committer in the know could put up a wiki page for
> committers asking these same questions. I feel stupid asking these
> things but, I'm not going to do anything until I know I'm doing it
> right.
>
> Mike
>
> Quoting Bertrand Delacretaz <bdelacre...@apache.org>:
>
>> On Tue, Oct 2, 2012 at 12:42 PM, Michael Schmalle
>> <apa...@teotigraphix.com> wrote:
>>> ...Could someone steer me to emails or something that says how a
>>> committer is
>>> supposed to take a JIRA task, fix it in their local code base and where to
>>> commit that code....
>>
>> I don't have that info, but if it's buried in emails that's probably
>> the wrong place IMO ;-)
>>
>> -Bertrand
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
