-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Produce Release Candidate #169
Comments
For me personally, I would only like to only add some TCK tests which can be done after RC if I'm not mistaken. The API is stable enough already. Minor tweaks if something is hit after RC should also be possible. Other specifications took between 3-5 months in RCs so I'm a big +1 on this! |
It does look like spec text changes and TCK tests rather than new functionality: https://github.com/eclipse/microprofile-lra/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0 is the scope of what is left. An RC would be great! |
FYI the CQs for the project are: [INFO] +- javax.ws.rs:javax.ws.rs-api:jar:2.0.1:provided |
I will have a go at creating the Jenkins job for the release when we have decided what to do with the outstanding API and spec PRs. |
@mmusgrov the amazon aws dependency is only required at runtime? At least not for compiling the TCK project. Is Amazon AWS S3 required for running the TCK, I don't see anything in the TCK readme. |
Thanks @rdebusscher - I have withdrawn the aws s3 cq and will remove the maven dependency from the tck pom when I submit the PR. |
FYI: The CQ for the arquilian junit dependency (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20313) is still awaiting PMC approval. Note that there is already an approved CQ for arquilian testng so we could easily migrate the TCK from junit to testng if it becomes an issue. |
Martin pointed out that the approved CQ 13755 (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13755) includes the arquillian junit dependency. I have withdrawn https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20313 and created a piggyback CQ for out test dependency: |
I don' think I needed a CQ for a "Works With Dependency" (CQ 13755) so I have withdrawn the piggyback CQ 20328 for the test dependencies. This means that we now have all the CQ approvals and we just need the final review of PR #176 |
RC 1 is tagged |
We need to have a RC available which can be tested out/used by the community during a couple of months before we can go final.
The text was updated successfully, but these errors were encountered: