RFR: 8257733: Move module-specific data from make to respective module
Magnus Ihse Bursie
magnus.ihse.bursie at oracle.com
Mon Jan 18 13:21:07 UTC 2021
On 2021-01-15 19:27, mark.reinhold at oracle.com wrote:
> Feature JEPs are living documents until such time as they are delivered.
> In this case it would not be appropriate to update JEP 201, which is as
> much about the transition from the old source-code layout as it is about
> the new layout as of 2014.
> At this point, and given that we’d already gone beyond JEP 201 prior to
> this change (with `man` and `lib` subdirectories), what’d make the most
> sense is a new informational JEP that documents the source-code layout.
> Informational JEPs can, within reason, be updated over time.
So I take it I need to create a new informational JEP. :-) Fine, I can
do that. I assume I mostly need to extract the parts of JEP 201 that
describes the (then "new") layout, update wording to show that this is a
description of the current layout, and add the new additions.
It'll be a very short JEP, but in this case, that's probably a virtue.
More information about the core-libs-dev