A crazy out-there suggestion...
Could OpenJDK work in partnership with stackoverflow on this through via
either a new tag - e.g.[javafx-possible-bug] or a whole new stackoverflow
site?
IMHO forums aren't the best way to work through coding problems, it's just
unorganised noise, the stackoverflow
On 15 April 2015 at 03:50, Kevin Rushforth
wrote:
> ...
> The issues currently in the RT project in JavaFX JIRA will be folded into
> the JDK project in JBS.
>
What about the Scene Builder issues (DTL project in JavaFX JIRA)? Would
they also be migrated to JBS?
--
Anirvan
My frustration isn't aimed at anyone on the list, so I hope it didn't seem
like that.
I don't usually post to the list, but I follow it enough to know that, once
we see an announcement like the one Kevin delivered, the decision has been
made and there's no going back. If I've misinterpreted, I ap
> Why can't an effort be made to influence JBS policies before making the
> switch?
I think the way to do this is to engage the JBS folks on their alias, I don’t
think they watch this one and Kevin doesn’t have the ability to change this
policy. He’s just the messenger!
Richard
Jira: https://javafx-jira.kenai.com/browse/RT-40533
webrev: http://cr.openjdk.java.net/~flar/RT-40533/webrev.02/
(note that this latest webrev is generated against 9-dev and has a few
lines/names/copyrights cleaned up, but no change in the logic...)
...jim
You don't mention what version of JavaFX you are using. Assuming you
have tested this issue against 8u40 and / or 8u60 EA builds, and if the
issue persists, then yes, please file an issue in Jira.
Thanks,
-- Jonathan
On 15/04/2015 11:53 p.m., Adam Granger wrote:
Hi, I've just asked this on s
On Wed, 15 Apr 2015 18:31:56 +0200, Ryan Jaeb wrote:
If someone submits a decent quality bug report to the forum, they could
be
invited to use JBA. ...
You could probably even come up with a strategy for letting the community
nominate people for JBS invites so the developers wouldn't have to
I will also add a suggestion that I think would be reasonable. Take
advantage of the OTN forum. Anyone without a JBS account could be asked to
post their first bug report to the forum. If it's not a bug, the forum
community can help with the issue. The forum community can also help
people learn
On Wed, 15 Apr 2015 17:55:19 +0200, Robert Krüger
wrote:
Understandable. IMHO a certain "seriousness threshold" to reduce the
noise
makes sense.
I was thinking on a score system such as the one at StackOverflow, but I'm
not aware of any support of Atlassian.
What if you at least had
What are the chances more open access policies will really be implemented? It
sounds to me like they really won't so it will cut off input from most people.
Costs will go down yes but unreported bugs will go up and users will have much
less sense of really being involved.
On Wed, Apr 15, 2
Keep in mind the cost cutting is going to be exaggerated and it's going to
be difficult to measure any long term damage this change will have on the
JavaFX community. People like me are going to stop participating.
There'll be fewer bug reports, it's going to take fewer people to manage
the bug lo
On Wed, Apr 15, 2015 at 4:54 PM, Richard Bair
wrote:
> Hi everybody,
>
> Moving to JBS is both good and bad. The good:
>
> The bad:
>
>- Contributing is hard (nay, impossible?) if you are not at least an
>OpenJDK Author
>
>
>
That's really the only (and serious) aspect anyone is complai
On 15.04.2015 04:58, Stefan Fuchs wrote:
So my question is, how does the web frontend process work at oracle?
Quoting from https://wiki.openjdk.java.net/display/general/JBS+Overview
"At the time of launch, self-service account creation is not supported.
Users without an account can browse J
On 15.04.2015 16:54, Richard Bair wrote:
Dalibor would probably know the right alias to discuss the JBS policy
Quoting from https://wiki.openjdk.java.net/display/general/JBS+Overview :
"General questions about JBS can be sent to disc...@openjdk.java.net.
Feature requests for JBS itself can
Hi everybody,
Moving to JBS is both good and bad. The good:
Reduce costs associated with the project
Reduce internal overhead for development processes (everybody on Java uses JBS
for everything so having a second JIRA makes everything harder with release
management, management, even engineers w
Hi, I've just asked this on stackoverflow, but I'm guessing someone from
this group might be able to help better... Should I raise a JIRA?
I've discovered what I believe is a memory leak in BarChart triggered by
replacing all the data values in the series. This is exasperated by our
application wh
Kevin Rushforth wrote:
A JBS account will be needed to directly report new bugs or comment on
existing bugs. Most application developers will file new JavaFX bugs at
bugs.java.com [3] just like other JDK bugs. The requirement to get a JBS
account [4] is to have a role of Author or higher in an O
Hi Kevin, Vadim,
Please have a look at the following fix in WebKit bridge/jni/jsc code:
JIRA: https://javafx-jira.kenai.com/browse/RT-37859
webrev: http://cr.openjdk.java.net/~ant/RT-37859/webrev.0
Thanks,
Anton.
I had not realized that ...
Just be safe that everybody here is aligned to the focus of the
discussion... As I previously said, I think the problem lies with the
access policy. From the JBS official page:
Account Eligibility
OpenJDK Roles, Groups, and Projects are explained in
On Wed, Apr 15, 2015 at 8:53 AM, Ryan Jaeb wrote:
> Do you guys have an estimate for the percentage of current JIRA
> contributors that will no longer be able to participate, in a meaningful
> way, in bug reporting due to this change? I can't speak for anyone else,
> but I can tell you what a sw
I think the confusing part of Kevin's mail was the "file to bugs.java.com" bit.
I think he meant for customers who already file bugs report to the
shipped-with-Oracle idk version of JavaFX, not the same OpenJFX we
discuss here.
OpenJFX bugs will be directed to the JIRA based https://bugs.openjdk.
On Wed, 15 Apr 2015 09:49:09 +0200, Tom Eugelink wrote:
I do not understand these doubts, JBS is Jira?!
https://wiki.openjdk.java.net/display/general/JBS+Overview
/The JDK bug system (JBS) ... is a JIRA instance which provides bug
tracking for Projects in the OpenJDK/
I think that this is
2015-04-15 8:32 GMT+02:00 Tobias Bley :
> Hi,
>
> in my opinion it’s definitely no good news to move from JIRA to JBS. While
> Jira is a very good and popular bug tracking system, the JDK JBS is a pain.
> With JBS the community efforts will decrease. It’s too complicated to be part
> of the Java
I do not understand these doubts, JBS is Jira?!
https://wiki.openjdk.java.net/display/general/JBS+Overview
/The JDK bug system (JBS) ... is a JIRA instance which provides bug tracking
for Projects in the OpenJDK/
On 15-4-2015 09:42, Fabrizio Giudici wrote:
While consolidating the issue tracke
While consolidating the issue tracked is a plus, I share the doubts about
the usability of JBS vs Jira. Why not going the opposite path :-) that is
consolidating everything under Jira?
--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it
On Wed, Apr 15, 2015 at 12:20 AM, Kevin Rushforth <
kevin.rushfo...@oracle.com> wrote:
>
>
> A JBS account will be needed to directly report new bugs or comment on
> existing bugs. Most application developers will file new JavaFX bugs at
> bugs.java.com [3] just like other JDK bugs. The requirement
26 matches
Mail list logo
