Asking for JEP 1 (and 2) to be revised to include details of JEP 2.0 Process Proposal

[David Alayachew]

Also, this would (necessarily) require folding the changes from JEP 2.0
Process Proposal into JEP 2, as listed in the bottom of the JEP 2.0 Process
Proposal.

*(Again, JEP 2.0 Process Proposal is not to be confused with JEP 1 or 2.)*

On Sun, Sep 7, 2025, 2:44 AM David Alayachew <davidalayachew at gmail.com>
wrote:

> Hello,
>
> At the very top of JEP 1, there is the following snippet.
>
> > *NOTE: Much of this document is*
> > *superseded by the JEP 2.0 Process*
> > *Proposal, in which JEPs are created and*
> > *maintained as a custom "JEP" issue type in*
> > *the JDK Bug System. Please see the*
> > *proposal for details. That proposal will*
> > *eventually be folded into this document.*
>
> After reading through 2.0 (not to be confused with JEP 2), it seems like
> 2.0's reason for existing is to communicate what details from JEP 1 have
> changed, now that we are using JBS instead of Mercurial to house the JEP's.
> It also appears that the "folding" has not yet completed.
>
> I am trying to *fully* understand the *current* "spec" of a JEP and the
> JEP Process, so wanted to make sure that I am looking at the right version.
>
> 2.0 only contains the details of JEP 1 that have changed. And while I am
> fine mentally "rebasing" the changes of 2.0 against JEP 1, I'd also prefer
> to look at a single source of truth.
>
> Could we complete the "folding" of JEP 2.0 Process Proposal into JEP 1? It
> seems like the process outlined in 2.0 is active and in use, but just not
> explicitly documented in JEP 1, other than the notice.
>
> Thank you for your time and help.
> David Alayachew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/discuss/attachments/20250907/828c5a17/attachment.htm>