Skip to content

QL 1.20 docs: Be more explicit about Java versions supported#1122

Merged
yh-semmle merged 2 commits into
github:rc/1.20from
felicitymay:1.20/SD-3061-java-versions
Mar 18, 2019
Merged

QL 1.20 docs: Be more explicit about Java versions supported#1122
yh-semmle merged 2 commits into
github:rc/1.20from
felicitymay:1.20/SD-3061-java-versions

Conversation

@felicitymay

Copy link
Copy Markdown
Contributor

This small text change makes the documentation more explicit about which Java versions are supported. This was triggered by a discussion on Slack.

@aschackmull or @yh-semmle - can you check this is clear and correct?

yh-semmle
yh-semmle previously approved these changes Mar 18, 2019

@yh-semmle yh-semmle left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, modulo one inline comment.


.. [1] The best results are achieved with COBOL code that stays close to the ANSI 85 standard.
.. [2] Java 11 refers to the language features used. Builds that execute on Java 6 or higher can be analyzed.
.. [2] Builds that execute on Java 6 or higher can be analyzed. The analysis understands Java 11 language features.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically, "Java 6 or higher" should say "Java 6 to 11" (builds executing on early-access versions of Java 12 are not yet supported).

@felicitymay

Copy link
Copy Markdown
Contributor Author

Thanks for the review. Topic updated accordingly.

@yh-semmle yh-semmle merged commit 13cd7d0 into github:rc/1.20 Mar 18, 2019
@felicitymay felicitymay deleted the 1.20/SD-3061-java-versions branch September 23, 2019 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants