After further discussion on the changes that were made to Diagnostic messages, we have decided to revert the Diagnostic.getMessage() behavior back to its original form and delay it's change until Daffodil 4.0.0. See https://github.com/apache/daffodil/pull/1493
With that said, I am canceling the vote for 3.11.0-rc1. There will be a 3.11.0-rc2 in the very near future. Josh Adams ________________________________ From: Adams, Joshua <jad...@owlcyberdefense.com> Sent: Thursday, May 22, 2025 1:25 PM To: dev@daffodil.apache.org <dev@daffodil.apache.org> Subject: Re: [VOTE] Release Apache Daffodil 3.11.0-rc1 +1 (binding) I checked all digital signatures, hashes, and checksums (see attached output). I also checked against roughly 80 different schema projects for any regressions. Found one case where the change to diagnostic messages caused some errors, but that is an expected breakage and easily fixed. See https://github.com/OpenDFDL/examples/pull/38 All other schemas behaved as expected. Josh Adams ________________________________ From: Adams, Joshua Sent: Wednesday, May 21, 2025 12:30 PM To: dev@daffodil.apache.org <dev@daffodil.apache.org> Subject: [VOTE] Release Apache Daffodil 3.11.0-rc1 Hi all, I'd like to call a vote to release Apache Daffodil 3.11.0-rc1. All distribution packages, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/daffodil/3.11.0-rc1/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachedaffodil-1051/ This release has been signed with PGP key 989D39300ACC1866, corresponding to jad...@apache.org, which is included in the KEYS file here: https://downloads.apache.org/daffodil/KEYS The release candidate has been tagged in git with v3.11.0-rc1. For reference, here is a list of all resolved JIRA issues tagged with 3.11.0: https://s.apache.org/daffodil-issues-3.11.0 For a summary of the changes in this release, see: https://daffodil.apache.org/releases/3.11.0/ Please review and vote. The vote will be open for at least 72 hours (Wednesday, 21 May 2025, 1:00 PM EST). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, - Josh
