[ 
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779876#comment-17779876
 ] 

Bryan Pendleton commented on DERBY-7157:
----------------------------------------

I've struggled with this same question myself. It wasn't obvious to me that 
10.17 was JDK 21+., either.

The way we've dealt with this in the past was to document things on 
[https://db.apache.org/derby/derby_downloads.html] , but that is getting 
increasingly clunky. For example, the top of the page where it says "For Java 8 
and higher", "For Java 9 and higher", etc. could easily make you think that the 
various releases have no known upper bound, but I don't think that's true.

Documenting the valid releases in multiple places will help with 
discoverability, but it might also be time to re-arrange that downloads page in 
a way which makes it more clear that some of these decades-old releases are in 
a different category. Perhaps a paragraph at the top covering the major 
boundaries (when Modules were released, when Security Manager was dropped, 
etc.)?

> Tasks for releasing Derby 10.17.1
> ---------------------------------
>
>                 Key: DERBY-7157
>                 URL: https://issues.apache.org/jira/browse/DERBY-7157
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>            Reporter: Richard N. Hillegas
>            Assignee: Richard N. Hillegas
>            Priority: Major
>         Attachments: derby-7157-01-aa-draftReleaseNotes.diff, 
> derby-7157-02-aa-initialSTATUSupdate.diff, 
> derby-7157-03-aa-updateDocConstants.diff, 
> derby-7157-04-aa-updateReleaseProperties.diff, 
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, 
> derby-7157-06-aa-newDataDictionaryVersion.diff, 
> derby-7157-07-aa-recordBranchesOnWebsite.diff, 
> derby-7157-08-aa-updateAntVersion.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to