New candidate JEP: 486: Permanently Disable the Security Manager

[Iris Clark]

The following JEP with scope "SE" has been moved to the Candidate state:

  486: Permanently Disable the Security Manager
  https://openjdk.org/jeps/486

    Summary: The Security Manager has not been the primary means of
    securing client-side Java code for many years, it has rarely been used
    to secure server-side code, and it is costly to maintain.  We therefore
    deprecated it for removal in Java 17 via JEP 411 (2021).  As the next
    step toward removing the Security Manager, we will revise the Java
    Platform specification so that developers cannot enable it and other
    Platform classes do not refer to it.  This change will have no impact
    on the vast majority of applications, libraries, and tools.  We will
    remove the Security Manager API in a future release.

A JEP in the Candidate state is a feature deemed worthy of consideration by
the JDK Project, but with no commitment to deliver the feature in any
particular release of the JDK Project. Later, the JEP may be moved to the
Targeted state, which indicates that the feature is expected to appear in a
specific release of the JDK Project.  For more information about states, see
the JEP Process document:

    https://openjdk.org/jeps/1

A JEP with "SE" scope that reaches the Targeted state will be listed in the
Specification of the Java SE Platform JSR which corresponds to the targeted
JDK Project release.

A dashboard that lists JEPs with "SE" scope may be found via a link on this
page:

    https://openjdk.org/projects/jdk/24/spec/

Thanks,
Iris