o: dev@daffodil.apache.org
Subject: EXT: [DISCUSS] Release Apache Daffodil 3.6.0 (or 3.5.1)
WARNING: This email originated from outside of GE. Please validate the
sender's email address before clicking on links or attachments as they may
not be safe.
It's been a few months since our last release, so I think it's
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
ations in some schemas around here
> after the change went in to fix these warnings, so I'm speaking from
> experience.
>
> John
>
> -Original Message-
> From: Steve Lawrence
> Sent: Wednesday, October 18, 2023 9:21 AM
> To: dev@daffodil.apache.org
> Subject: EXT: [D
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
] Release Apache Daffodil 3.6.0 (or 3.5.1)
WARNING: This email originated from outside of GE. Please validate the sender's
email address before clicking on links or attachments as they may not be safe.
It's been a few months since our last release, so I think it's about time for
our next one
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
