[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jms-dev] Preparing for final release
|
Thanks again, Kevin.
This has now been fixed thanks to a PR from Hussain (thank you Hussain!). Javadoc regenerated and PR updated:
- https://github.com/jakartaee/specifications/pull/256
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Oct 23, 2020, at 5:19 AM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
>
> Thanks, David!
>
> I found one more minor item that should be easy to fix. The Copyright on the Javadoc states 2019, no mention of 2020. Hopefully, this is easy to update and we can still start the ballot today. Thanks again!
>
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect @ IBM
> e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
>
>
>
> From: David Blevins <dblevins@xxxxxxxxxxxxx>
> To: jms developer discussions <jms-dev@xxxxxxxxxxx>, Kevin Sutter <sutter@xxxxxxxxxx>, Ed Bratt <ed.bratt@xxxxxxxxxx>
> Date: 10/22/2020 22:20
> Subject: [EXTERNAL] Re: [jms-dev] Preparing for final release
>
>
>
> Thanks, Kevin for the review on our spec PR! All should be updated. I did not cut a new...
> This Message Is From an External Sender
> This message came from outside your organization.
>
> Thanks, Kevin for the review on our spec PR!
>
> All should be updated.
>
> I did not cut a new release for the javadoc as I didn't want to trigger any additional TCK work. There was no change needed in source other than fixing the 2.0->3.0 reference; a plain `mvn javadoc:jar` does create javadoc with the appropriate licensing, footer and version in upper right corner. It's been like that since 2019. I do not know why the staged javadoc jar does not contain it, nor does the RC1 javadoc jar contain it.
>
> I find that a little unsettling, but it'll take some effort to find the cause and I'm nervous about holding up the release. I suspect there may be something up in the jenkins setup. It does appear however the API jar itself is good, passes the signature tests and TCK, so I think pragmatically we're ok though not ideal.
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> On Oct 21, 2020, at 7:52 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
>
> Ed,
>
> I just marked the certification request you filed as approved, updated our PR with the new SHA and the updated the index.md with the new compatible implementation links. Consider this the official nod from the spec project to the mentor that we think we're ready to go.
>
> Have a look and let me know if there are any adjustments. Thank you for all the heavy lifting on this one; you really were more of a spec project member than mentor. It's very very appreciated.
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>
> On Oct 20, 2020, at 8:53 PM, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:
>
> Also, there's a TCK Results Summary already in place in OpenMQ. All it needs are the final pointers and it's good to go.
>
> https://eclipse-ee4j.github.io/openmq/certifications/jakarta-messaging/3.0/TCK-Results
>
> On 10/20/2020 8:48 PM, Ed Bratt wrote:
> I believe GlassFish 6 RC1 contains the jms-api version is 3.0.0-RC1. Is that what we want? We can use Open MQ -- (for the ballot, that's perfectly good compatible implementation). This job here, runs the stand-alone TCK against Open MQ all by itself. However, we need to get the MetaData tests to pass by upgrading the TCK to use 3 as the expected API version and fix this issue.
>
> -- Ed
>
> On 10/20/2020 6:42 PM, David Blevins wrote:
> It seems there's an RC1 of GlassFish we could use for the Compatible Implementation request we need to complete our PR:
>
> - https://github.com/jakartaee/specifications/pull/256
>
> Tomorrow I plan to hunt it down and see if we can get a TCK run against it using our promoted TCK. Assuming all that goes we'll, we should be good to prepare the certification request and once that is added to the GlassFish website, we can let the our mentor know to start the ballot.
>
> Ideally we have a ballot up by Friday.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>
>
> _______________________________________________
> jms-dev mailing list
>
> jms-dev@xxxxxxxxxxx
>
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jms-dev
>
>
>
>
> _______________________________________________
> jms-dev mailing list
>
> jms-dev@xxxxxxxxxxx
>
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jms-dev
>
>
>
>
>
>