I'll ping them. We can keep the current state and present Oracle alone in GUI and logs, as it is done now.
It's cosmetic/non-functional, but I can't assess its [un]importance.
That would be good to have sorted, but as mentioned, the review takes time and can't be done instantly in most cases. I can only really send the IP log until the last commit for this release has been done, so the sooner the better. I've now updated the release date to 4 december, but this means the last commit intended for it needs to be in way before that.
But I think we could prepare RC1 from the current master, with this one #608 to be considered for final, just to go through TCK.
I can click through Jenkins for that. On passing TCK I can submit a draft PR for GF to have GF run its pipeline with RC.
Unless someone else wants to do it too.
Doing the RC1 would not hurt indeed, if you want, please go ahead.
Kind regards,
Arjan
On Thu, 19 Nov 2020 at 17:07, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
It’s not too late to make the GlassFish 6.0.0 final release as that is not until December 8th.
Hi,
Last month we did the 6.0.0-M3 release. I think we shouldn't wait too long anymore to do the 6.0.0 final release. We're likely already a bit too late for making it into the GlassFish 6.0.0 release.
_______________________________________________
openmq-dev mailing list
openmq-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/openmq-dev
_______________________________________________
openmq-dev mailing list
openmq-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/openmq-dev