JavaFX JIRA issues moving to JBS Friday, June 12

We are on track to perform the migration of FX JIRA issues to JBS this Friday, June 12. The RT project in the JavaFX JIRA issue tracker will become read-only at 9:00 am Pacific time Friday morning. JBS planned downtime is from 1:00 pm - 5:00 pm Pacific Friday afternoon, after which JavaFX bu

RESCHEDULED -> Re: Reminder: JavaFX JIRA issues moving to JBS tomorrow, June 5

Due to a bug discovered in the migration script during the dry run, we will need to reschedule the migration. Exact date TBD as we will need to re-run series of testing. Our tentative target will be next Friday, June 12. Once confirmed, we will send another heads-up notice. -- Kevin Kevin

Reminder: JavaFX JIRA issues moving to JBS tomorrow, June 5

As a reminder, the migration of FX bugs to JBS will happen tomorrow. The RT project in the JavaFX JIRA issue tracker will become read-only at 9:00 am Pacific time tomorrow morning. We expect the migration to be complete some time in the afternoon tomorrow. Also, our infrastructure team is plan

Re: JavaFX JIRA issues moving to JBS on June 5

Has any progress been made regarding the issues raised by a number of people (mainly bug report contributors and followers), i.e. are policy changes regarding JBS accounts or new types of JBS accounts for that purpose something that is likely? Is anyone in the JFX team lobbying for this? On Fri, M

JavaFX JIRA issues moving to JBS on June 5

As previously announced [1] we are in the process of migrating JavaFX bugs to the JDK Bug System (JBS) [2] in the JDK project. The target date for this migration is Friday, June 5. The existing JavaFX bug tracker will become permanently read-only on that date, and will be decommissioned some t

Re: JavaFX JIRA issues moving to JBS

Of course I forgot to be explicit about the main thing that was important to the discuss alias when I posted that last message. You do NOT need to sign the OCA to contribute a bug via bugs.java.com. I'm not actually sure why the page at bugs.java.com directs people to the contributor agreement be

Re: JavaFX JIRA issues moving to JBS

I want to highlight something that was clarified for me on the discuss alias. On the bugs.java.com page there's a section entitled "Submit a Code Fix or Test Case". I misinterpreted it to be part of the guidelines for submitting a bug and have been under the impression that I would be required to

Re: JavaFX JIRA issues moving to JBS

On Wed, Apr 15, 2015 at 10:54 AM, Richard Bair wrote: > This is exactly the issue. We know from the last 20 years that in fact we get > a huge amount of completely bogus bugs that get filed via bugs.java.com > (previously bugs.sun.com ). > Wild stuf

Re: JavaFX JIRA issues moving to JBS

I started a thread over there just before I saw these last couple replies. http://mail.openjdk.java.net/pipermail/discuss/2015-April/003719.html Ryan Jaeb On Thu, Apr 16, 2015 at 6:35 AM, Fabrizio Giudici < fabrizio.giud...@tidalwave.it> wrote: > On Thu, 16 Apr 2015 14:01:03 +0200, Kevin Rushf

Re: JavaFX JIRA issues moving to JBS

Not in this initial phase, mainly due to the tight schedule and amount of work involved, but likely in a follow-up phase. -- Kevin Anirvan Sarkar wrote: On 15 April 2015 at 03:50, Kevin Rushforth > wrote: ... The issues currently in the RT project i

Re: JavaFX JIRA issues moving to JBS

I was talking to Phil about a related point yesterday. One thing we (the JavaFX developers at Oracle) will need to do is to take a more active approach in helping bugs filed at bugs.java.com make their way from the internal "Incidents" project into the JDK project as an active bug. This doesn't

Re: JavaFX JIRA issues moving to JBS

On Thu, 16 Apr 2015 14:01:03 +0200, Kevin Rushforth wrote: Exactly. This is an OpenJDK policy issue. Dalibor posted the link to the discuss alias that you might send an e-mail to. So, ok, this specific discussion should move there. I subscribed to the ml pointed by Dalibor, all the one i

Re: JavaFX JIRA issues moving to JBS

Exactly. This is an OpenJDK policy issue. Dalibor posted the link to the discuss alias that you might send an e-mail to. -- Kevin Richard Bair wrote: 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

Re: JavaFX JIRA issues moving to JBS

On Thu, 16 Apr 2015 11:57:10 +0200, Robert Krüger wrote: Please note that the main criticism is not that it becomes a problem for code contributors but for people submitting qualified bug reports including reproducible test cases, concrete measurements etc. or contribute these kind of thin

Re: JavaFX JIRA issues moving to JBS

On Thu, Apr 16, 2015 at 11:02 AM, Mario Torre < neugens.limasoftw...@gmail.com> wrote: > > On the other end, the rules for Author are clear, you need to sign the > OCA (this is the main pain point, but I believe most of the > contributors to OpenJFX already have this done anyway, isn't that a > re

Re: JavaFX JIRA issues moving to JBS

As a long time OpenJDK contributor I agree the fact of needing to be an Author to file bug reports is an inconvenience. This is something that is discussed basically at every public meeting where the Governing Board is present (particularly at Fosdem, sometimes at Java One as well). For OpenJDK A

Re: JavaFX JIRA issues moving to JBS

On Thursday, April 16, 2015, Ryan Jaeb wrote: > 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 > ma

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

> 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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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.

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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

Re: JavaFX JIRA issues moving to JBS

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 switch to JBS means to me. I consider myself an OpenJFX user,

Re: JavaFX JIRA issues moving to JBS

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 community if you are forced to first sign a commit

Re: JavaFX JIRA issues moving to JBS

Hi Kevin, while I appreciate the consolidation of the bug tracking systems, I have some questions about the JBS. Having filed some jdk-bugs via bugs.java.com in the past, I never got any feedback, if the bug has been accepted and if an JDK bug has been created. For example three weeks ago,

Re: JavaFX JIRA issues moving to JBS

2015-04-15 0:20 GMT+02:00 Kevin Rushforth : > As part of this transition, we will enable anonymous viewing of bugs (no > need to login just to look at a bug) and they will be easily searchable > online. Great news! Cheers, Mario -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerpr

JavaFX JIRA issues moving to JBS

As most of you are aware, JavaFX uses its own JIRA bug tracker [1]. The JDK Bug System [2] (JBS) is the JIRA bug tracker used by the OpenJDK Community. With the OpenJFX Project being a part of this Community, it is time for us to move away from our separate bug tracker and make use of JBS. This