Ok, well @slawre...@apache.org <slawre...@apache.org> has a PR with this issue fixed waiting for a 2nd +1.
This (or similarly labeled) thread(s) have been open since 2021-11-01. All issues raised in these threads are now resolved (or we believe they are, and that will get verified when we evaluate the RC). So I believe we can proceed to create the release candidate. I volunteer to be the release manager. I'll start once this final PR to fix the DAFFODIL-2579 issue gets merged. On Mon, Nov 29, 2021 at 10:33 AM Steve Lawrence <slawre...@apache.org> wrote: > I think it just comes down to if we want to support that kind of > backwards compatibility. > > It doesn't feel high priority to me as long as our pre-built convenience > binaries are always Java 8 compatible. Users building from source should > hopefully be aware of Java compatibility issues and build/run with the > same Java versions. > > I've updated DAFFODIL-2579 with a little more background of what's going > on and a potential fix if we do want to always ensure compatibility. > > On 11/29/21 9:23 AM, Thompson, Dave wrote: > > If a daffodil build on java 17 is supposed to be backwards compatible > with a system running java 8, then I would think this would be a bug. > > > > Dave > > > > -----Original Message----- > > From: Steve Lawrence > > Sent: Monday, November 29, 2021 8:17 AM > > To: dev@daffodil.apache.org > > Subject: Re: [DISCUSS] ready to release 3.2.0? > > > > It's not clear to me if that's a bug or not, but even if it is I don't > think it should affect the release. The release candidate container builds > with Java 8, so won't have this issue of building on a new Java but running > with an older. I think it should be fine to bump this bug to the next > release and start the process of releasing 3.2.0. > > > > On 11/24/21 1:11 PM, Mike Beckerle wrote: > >> We have only this issue marked as for release 3.2.0: > >> https://issues.apache.org/jira/browse/DAFFODIL-2579 > >> > >> I am not sure this is a bug. Please review it. > >> > > > >
