fx 1.x issues in JBS
kevin.rushforth at oracle.com
Tue Jan 16 01:00:53 UTC 2018
For practical purposes you can treat resolved and closed as the same.
Resolved/fixed versus Closed/fixed does indeed mean what you think, but
the majority of bugs are never verified, so that difference is really
only of interest to the testing organization. I always treat them as the
same in all filters (thus use "resoltuion is EMPTY" to look for open
bugs, resolution = "Fixed" to looked for fixed bugs, etc., and don't
query on the status for Resolved or Closed).
Nir Lisker wrote:
> I see, was not aware that there are enough similarities between 1.x
> and later versions. About Resolved issues, I thought that they are
> waiting for a fix confirmation to be Closed.
> On Mon, Jan 15, 2018 at 5:29 PM, Kevin Rushforth
> <kevin.rushforth at oracle.com <mailto:kevin.rushforth at oracle.com>> wrote:
> While I suspect many of them can be closed out at this point, it
> is not necessarily a given that they are irrelevant (the scene
> graph, animation, and graphics engine evolved from 1.x to 2.0). I
> agree that it would be good to take a pass over them and close out
> the ones that are no longer issues, but I they can't simply be
> closed out as a bulk close operation without looking at them.
> Also, you say "a lot in resolved" my response would be that I hope
> so. An issue that is resolved needs no more action and won't show
> up in searches for open bugs. So I guess I'm not sure what you
> mean by this.
> -- Kevin
> Nir Lisker wrote:
> JBS still has open issues for JavaFX 1 versions and they
> appear in searches
> even though there's nothing to do about them since that
> version is not
> supported anymore. Is it appropriate to close them all? There
> are also a
> lot in Resolved.
> - Nir
More information about the openjfx-dev