Re: [jms-dev] CI/CD Pipeline for JMS
|Hmm, I don't appear to have admin on the repo to fix this. I'll follow up with the rest of the PMC.
David, it seems the JMS repo is also set up slightly different from others.
Not sure, if it's intended, but there is no requirement to approve a PR by a reviewer. Since those kinds of things must be done by a owner or PMC member, please check it. In a particular case only a README file had a typo fixed, I guess it is acceptable, for others I would have requested a review before merging it, but maybe you should check the repo to align it with the others.
I didn't fully understand the response.
Are there things we need to do from the JMS spec side to support the release of OpenMQ?
Thanks for the message. I think the CI pipeline should be set up now or soon. If the Jenkins instance is already there, happy if someone wanted to create jobs there.
Also since a new bug was just filed against OpenMQ, I know it probably is of no interest to you or Tomitribe (I assume you may be using ActiveMQ of some kind instead of the current RI) but the version strategy for OpenMQ is also a bit messy, see https://github.com/eclipse-ee4j/openmq/issues/417
A 5.2.0 release review by Eclipse has been scheduled but there is not even a codebase that would work for that.
Both EE4J_8 and master say "5.1.2-SNAPSHOT" right now. I would assume, that's for the EE4J_8 branch, but not entirely sure.
The project has neither release nor tag, so not sure who planned that review or what code it should contain?
Hey Werner, I know you've already started digging into this. Happy to let you have fun with it, but if you need/want any help I can carve out some time to collaborate on it.
Description: Message signed with OpenPGP