Dear All,
JSR 380 Spec Lead Gunnar Morling just mentioned VisualVM had migrated from
java.net to GitHub:
https://visualvm.github.io/
A project officially run and hosted by Oracle. Is it safe to assume, others
will follow, or do other migration plans exist especially for Java EE
(Glassfish) related projects and JSRs?
JSR 375 is actually in a rather lucky position since it's relatively new
and has not so much history on java.net as other JSRs.
JIRA is used by JSR 375, but 36 tickets as of now seem like they could be
migrated to e.g. GitHub issue tracker without a massive effort.
Waffle (see
https://waffle.io/unitsofmeasurement/unit-ri for JSR 363 RI, it
only recently moved from JIRA, so there are not so many tickets, as the JSR
is final, we may stick to the tarball or other archives for historic
tickets) allows to put an "agile" layer and it's probably not the only
solution of that kind for the GitHub tracker.
Btw. as of Friday, the Spec Lead change was updated on jcp.org :-)
WDYT?
Werner