The information listed on this page will be assembled as a recommended process for presenting new features to the Apache Flex development group. This recommended process is not required due to Apache allowing new changes as "commit-then-review". However using this discussion process will assist in identifying any bugs, complications, or suggestions that may arise during the discussion.

Preparation

Recommended preparation prior to presenting the new feature.

  • Make sure any new files being added to the Flex-SDK have the correct Apache license in the header.
  • Host your example source code, so others may see how your implementing the new features and play with it themselves. An easy way to do this can be enable the "View Source" feature in your example application.
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                   xmlns:s="library://ns.adobe.com/flex/spark"
                   viewSourceURL="mysource.mxml.txt" >
  • Host the new or modified file changes to the Flex-SDK where others may view them. Currently GitHub makes an excellent place to host source code. There is a currently a discussion about shared whiteboard space within Apache Flex, however a final decision has not been made yet.

Starting the discussion

  • Start a new thread in the Dev email list. Prefix the email subject with [Example] and put your features name after it.
  • Add a description of what the feature is and what it does.
  • Add the links to your example and source code.

Discussion

  • The discussion allows for any bugs, complications, or suggestions to be presented and addressed if needed.
  • No vote is required to continue adding the feature into the SDK under normal discussion. However if there are parts of your new feature change that are under strong debate a vote maybe required to allow the Flex community to help decide.

Adding the new Feature

  • Create a new JIRA issue
  • Create new local branch with the JIRA issue number (FLEX-12345)
  • Make sure the commit changes comments are prefixed with the issue number.
  • No labels