Re: derby 10.17.1 release?
Much appreciated, Bryan. On 10/26/23 5:34 PM, Bryan Pendleton wrote: Short progress report: - I've successfully tested the distribution on Linux Ubuntu 20.04 with OpenJDK 21. - I've verified the signatures and checksums on the distribution I'm going to try to find time this weekend to do some testing with both Windows 10 and Windows 11. Thanks for getting the RC together so quickly, Rick! bryan On Mon, Oct 9, 2023 at 1:05 PM Rick Hillegas wrote: I volunteer to be release manager for 10.17.1. I have posted a schedule for this release: https://cwiki.apache.org/confluence/display/DERBY/DerbyTenSeventeenOneRelease . I expect to post the first rev of release notes next Monday (2023-10-16). If all goes well, the release should be published by 2023-11-10. Thanks to everyone who has volunteered to vet this release. -Rick On 10/2/23 9:46 AM, Rick Hillegas wrote: Our last release is dated May 2022. Would anyone be willing to vet a new release if I produce it? The key features would be support for the new LTS version of Java (Java 21) plus a security fix we worked on earlier this year. Thanks, -Rick
Re: derby 10.17.1 release?
Short progress report: - I've successfully tested the distribution on Linux Ubuntu 20.04 with OpenJDK 21. - I've verified the signatures and checksums on the distribution I'm going to try to find time this weekend to do some testing with both Windows 10 and Windows 11. Thanks for getting the RC together so quickly, Rick! bryan On Mon, Oct 9, 2023 at 1:05 PM Rick Hillegas wrote: > > I volunteer to be release manager for 10.17.1. I have posted a schedule > for this release: > https://cwiki.apache.org/confluence/display/DERBY/DerbyTenSeventeenOneRelease > . I expect to post the first rev of release notes next Monday > (2023-10-16). If all goes well, the release should be published by > 2023-11-10. > > Thanks to everyone who has volunteered to vet this release. > > -Rick > > On 10/2/23 9:46 AM, Rick Hillegas wrote: > > Our last release is dated May 2022. Would anyone be willing to vet a > > new release if I produce it? The key features would be support for the > > new LTS version of Java (Java 21) plus a security fix we worked on > > earlier this year. > > > > Thanks, > > > > -Rick > > >
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779853#comment-17779853
]
Knut Anders Hatlen commented on DERBY-7157:
---
Hi Rick,
This part of the 08-aa patch should probably not have been backported to the
10.17 branch:
{code:java}
--- RELEASE-NOTES.html (revision 1913211)
+++ RELEASE-NOTES.html (working copy)
@@ -177,11 +177,11 @@
Derby release 10.17.1.0 was built using the following environment:
-Branch - Source code came from the 10.17 branch.
+Branch - Source code came from the 10.18 branch.
{code}
It's not important enough to spin a new relase candidate, I think, but it would
be good to have it fixed in the branch in any case.
> 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)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779861#comment-17779861 ] Knut Anders Hatlen commented on DERBY-7157: --- We could probably have added a sentence to the release notes stating explicitly that we drop support for JDK versions prior to JDK 21. Just to avoid surprises. (I was caught by this myself, when I first tried to use the release candidate with JDK 17, and realized I had to install a newer JDK to get it working.) I suppose the download page will say "For Java 21 and Higher" when we make the new version available there, similar to what it says for other versions, so it's probably not a big issue in practice. (I assume dropping support for JDK 17 was intentional, and not just that we have forgotten to set the correct target version in the build scripts.) > 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)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780033#comment-17780033 ] Richard N. Hillegas commented on DERBY-7157: Responding to Knut and Bryan's comments about the confusing state of what Java versions 10.17.1.0 supports: The Overview section of the release notes does state that 10.17.1.0 runs on Java SE 21 and higher. For future release notes, to reduce confusion, should we explicitly state what Java versions the release won't run on? How can we make this clearer? Responding to Knut's comment about deprecating support for JDK 17 and earlier: Support was deprecated because the Open JDK has deprecated support for the SecurityManager in such a way that we had to change our instructions for how to boot Derby. We thought that continuing to support a deprecated feature was going to cause us trouble going forward and would make our user documentation confusing. Responding to Bryan's comments about the download page: As far as I know, there is no upper bound yet on the Java platforms which any of our releases support. Caveat: however, in order to run an old Derby version on a modern platform, you may have to change your boot command. We don't document what you need to do. Instead, if you want to use the SecurityManager, you have to boot Derby according to the documentation, trip over a fatal error from the JVM, google up that error message, and adjust your boot command accordingly. At some point, the Open JDK will actually rip out the SecurityManager. That change may impose an upper bound on the Java platforms supported by old Derby versions--I don't know, I think it depends on how the Open JDK handles the code removal. I like Bryan's suggestion about adding some verbiage concerning Modules and the deprecated SecurityManager. This would help users understand why we introduced lower bounds on platform support. > 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, > derby-7157-09-aa-goofProofBranchName.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-09-aa-goofProofBranchName.diff > 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, > derby-7157-09-aa-goofProofBranchName.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780009#comment-17780009
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-09-aa-goofProofBranchName.diff. This patch changes the
ReleaseNoteGenerator program so that extracts the branch name from the
user-supplied release ID rather than from subversion-controlled information.
Touches the following files:
{noformat}
M java/build/org/apache/derbyBuild/GeneratorBase.java
M java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java
Changes to the release note generator.
M RELEASE-NOTES.html
Regenerated release notes for 10.17.1.0.
{noformat}
> 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,
> derby-7157-09-aa-goofProofBranchName.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779975#comment-17779975 ] Richard N. Hillegas commented on DERBY-7157: Thanks for reading the release notes carefully, Knut. The branch name mistake happened because: 1) I built the release notes on trunk rather than the 10.17 branch. 2) There is a weakness in the ReleaseNoteGenerator program. It gets the branch name from the source code tree. I think it would be better if the program extracted the branch name from the user-supplied release ID. I will correct that weakness and regenerate the release notes. Then, at least, the branch name will be correct in the 10.17 branch and the process will be more goof-proofed going forward. > 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)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780010#comment-17780010 ] ASF subversion and git services commented on DERBY-7157: Commit 1913355 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1913355 ] DERBY-7157: Change the way that the ReleaseNotesGenerator determines the branch name; commit derby-7157-09-aa-goofProofBranchName.diff. > 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, > derby-7157-09-aa-goofProofBranchName.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
