Updates to config/mailinglist/rules/jdk.json related to compiler-dev and kulla-dev.

[lahodaj]

…and kulla-dev.

I tried to keep the sensible stuff, sending to multiple lists where in a real doubt. Some other javac/javadoc maintainers may disagree with some of the choices, though.

---

Progress

• Change must not contain extraneous whitespace
• Change must be properly reviewed

Reviewers

• Robin Westberg (rwestberg - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/skara pull/748/head:pull/748
$ git checkout pull/748

[bridgekeeper]

👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request.

[lahodaj]

I think this shows the question on maintenance from the jdk-dev list - the (internal) PreviewFeature may be moved to a different (internal) place sometime in the foreseeable future. Who will be updating this list?

[rwestberg]

When in doubt, I think it's better to err on the side of caution, so perhaps it should not be included in the list at all. But will expand on this in the jdk-dev thread.

[mlbridge]

Webrevs

• 00: Full (3d59181)

[rwestberg]

Thanks for the update!

[openjdk]

@lahodaj This change now passes all automated pre-integration checks. When the change also fulfills all project specific requirements, type /integrate in a new comment to proceed. After integration, the commit message will be:

Updates to config/mailinglist/rules/jdk.json related to compiler-dev and kulla-dev.

Reviewed-by: rwestberg

• If you would like to add a summary, use the /summary command.
• To credit additional contributors, use the /contributor command.
• To add additional solved issues, use the /issue command.

Since the source branch of this PR was last updated there has been 1 commit pushed to the master branch:

• aca3439: 542: Adjust label (cc) command logic

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge master into your branch, and then specify the current head hash when integrating, like this: /integrate aca3439640f72b6c3a6da5b8789ce10cbe7bd6d1.

As you do not have Committer status in this project, an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@rwestberg) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[lahodaj]

/integrate

[openjdk]

@lahodaj
Your change (at version 3d59181) is now ready to be sponsored by a Committer.

[rwestberg]

/sponsor

[openjdk]

@rwestberg @lahodaj The following commits have been pushed to master since your change was applied:

• aca3439: 542: Adjust label (cc) command logic

Your commit was automatically rebased without conflicts.

Pushed as commit 92a9799.