How does JFX work get prioritised?

Richard Bair richard.bair at
Fri Nov 2 13:36:39 PDT 2012

> If you want story point support there's a plugin for JIRA called
> Greenhopper ( that
> does the trick.  But from what I've seen so far, the Oracle SDLC is not
> agile, and not likely to become moreso any time soon.

Actually we use a lot of agile principles in our sprint planning and such. We have been looking at the whole range of Atlassian products for a (long) while including Greenhopper. For now though we've used Confluence for most of our planning. We're actively rewriting our processes to use the wikis on instead, so that this information is available. Often the sprint plans are viewable directly in JIRA (although it is custom per team). When we've gotten past the security / open source tasks, getting the process / etc all nailed down will be the top priority. Just by means of time frame, my expectation is that sometime in February next year we'll be fully complete with the open source process, including creating necessary mailing lists, consolidating information on the wiki, updating all the project pages, getting the repos properly hosted etc.

By then we'd better be done, because we'll be neck deep in bug fixes for the 8 release.

> Depending on the culture of open source projects, one of the approaches
> that HAS worked in the past involves commitment from both ends of the
> equation.  The person reporting the bug or feature request provides a patch
> that fixes the problem and a unit test that demonstrates the problem and
> demonstrates the fix.  Those kinds of issues get a higher priority because
> they are usually quicker to fix.  In this particular case, SQE could give
> feedback to the person providing the patch and unit test, in case there's
> some corner case that didn't get coverage.  The person providing the patch
> and SQE would run the entire test suite to make sure that no regressions
> were introduced.  If everything looks ok, the patch and unit test are
> committed, and you see the result in the nightly build.

Our view is that we need to get all the tests into the hands of all developers (both inside & outside Oracle), and all information to all users (both inside and outside Oracle). There are of course some things that won't be opened up (specific tests cases sent confidentially from companies, security issues, etc) but 98% or so of the entire project & process can and will be opened up.


More information about the openjfx-dev mailing list