Re: [DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1)

2023-10-18 Thread Shearer, Davin
Hi Steve, +1 for 3.5.1. Sounds like a patch version release to me. -Davin From: Steve Lawrence Date: Wednesday, October 18, 2023 at 9:20 AM To: dev@daffodil.apache.org Subject: [DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1)

Re: [DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1)

2023-10-18 Thread Mike Beckerle
I withdraw my prior statement. I'm convinced by John's reasoning that 3.6.0 is a better choice. On Wed, Oct 18, 2023 at 10:00 AM Interrante, John A (GE Aerospace, US) < john.interra...@ge.com> wrote: > Yes, I have some C code generator changes that I haven't had time to > collect into a PR yet.

Re: [DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1)

2023-10-18 Thread Mike Beckerle
I think 3.5.1 is the right number, as that is consistent with our odd-bug fix, even-features convention on the 2nd component of the version number. So 3.6.0 should be for the next addition of true new features. On Wed, Oct 18, 2023 at 9:20 AM Steve Lawrence wrote: > It's been a few months

RE: [DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1)

2023-10-18 Thread Interrante, John A (GE Aerospace, US)
Yes, I have some C code generator changes that I haven't had time to collect into a PR yet. I would like to get them into this release, so they don't have to wait for the next release. The deprecation of relative schemaLocation outputs new warnings which I think warrants a minor version bump.

[DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1)

2023-10-18 Thread Steve Lawrence
It's been a few months since our last release, so I think it's about time for our next one. If there are no objections, I'd like to start the release process early next week. Does anyone have changes they were hoping to get into this release, or know of any critical issues that should be