eparate doc repo (not co-located with the code)
- ??
What do you think?
-andy
*From: *openjfx-dev on behalf of
Michael Strauß
*Date: *Friday, August 9, 2024 at 07:31
*To: *
*Cc: *openjfx-dev@openjdk.org
*Subject: *Re: No Place for JEPs
Hi Andy,
wouldn't these documents risk getting
ew / keep track of
changes / lack of co-location)
- separate doc repo (not co-located with the code)
- ??
What do you think?
-andy
From: openjfx-dev on behalf of Michael Strauß
Date: Friday, August 9, 2024 at 07:31
To:
Cc: openjfx-dev@openjdk.org
Subject: Re: No Place for JEPs
Hi Andy,
Hi Andy,
wouldn't these documents risk getting outdated when the codebase is
evolved? JEPs seem to be most relevant at the time when a feature is
proposed. I think I'd rather have documentation colocated with the
code itself, this makes it easier to keep the documentation in sync
with the actual i
Dear fellow developers:
We often create JEPs and JEP-formatted documents as we propose and develop new
features. These help us during the review process and I am sure are of some
benefit for application developers as they try to learn the new functionality
in depth. Presently, we've been crea
