Page History

Recent Unresolved Issues

These are bugs that have been entered into the system recently and may either be an issue with the last release of Flex or an issue that may of been about for some time. Either way it's a bug someone cares about and have taken the time and effort to submit a JIRA report. First off check that the issue exists in the latest release of Apache Flex, it may be that the issue has already been solved, if so marked it as resolved or add a comment saying it's no longer an issue. IF the issue still exists use the supplied test application or create one yourself than simply demonstrate the issues and try and fix the issue in the codebase.

Link for Recent unresolved issues

Important Issues

These are bugs that people have marked as blockers or critical issues. You should consider trying to fix these issues before fixing other issues.

Link for Important issues

Popular Issues

These are bugs that people have marked have voted on and give an indication of how many people are interested in getting an issues resolved. You should consider trying to fix bugs with a large number of votes before fixing other issues.

Link for Popular issues

"EasyTest" Bugs

These bugs are generally older bugs. Ones that probably have been imported from the old Adobe issue tracking system before Adobe Flex was donated and became Apache Flex. These bugs need to be tested, to make sure they are still cause trouble. They generally will have a comment that explains what has failed and how it was found.

You will need to create a test application using the latest nightly Flex SDK to confirm them and post your results as a comment back into the issue. Sometimes the correct answer can be it's no longer an issue.

Link for Easy Test issues

"EasyFix" Bugs

These are bugs that not only are easy to test for, but may have an easy solution. If you wish to work on one of these, simply add a comment to the issue stating you are going to work on it or assign the bug to yourself. Next you will need to create a test application to confirm it still is an issue and it will let you know when you've fixed it, some of these bugs will already have code that demonstrates the bug. Make sure to use the latest nightly Flex SDK when working on the issue to check that the bug hasn't been already fixed. Once completed, create a patch and attach it to the issue with any comments you may have.

Link for Easy Fix issues

Closed and Later Issues

Adobe closed and mark to do later many bugs. Many of these bugs could still be issues that need to be resolved. If you find an bug that has A JIRA issue marked closed and later, ask for it to be reopened. You might also want to look though the list of closed and later bugs for bugs to work on or new functionally to implement.

Link for Closed and later issues

Issues with Patches

Some issue have patches supplied but these patches have not been tested or applied to the SDK. Take the patch form the JIRA issue and apply and test the patch. If the patch works resolved the issue or add a comment to the JIRA issue saying that the patch works.

Link for Issues with patches

Apache Flex Issues

Some issues are more recent issues raised by the wider Apache Flex community and may include regression issues form previous versions of Apache or Adobe Flex. These are bug that someone cared about enough to raise a JIRA issue in recent time (as opposed to old bugs that were imported from Adobe's bug base) and is a good list to find bugs to work on.

link for Unresolved Issues by people