I guess I have found issues indicating we are not quite ready for release. These may be caused by incompatibilities of the tests, but Owl has a regression test rig where we have every DFDL schema we can get our hands on.
I ran this for daffodil 3.1.0 and all tests pass. For daffodil 3.2.0-SNAPSHOT I get failures for these: [error] (dfdl-vmf-spock / Test / test) sbt.TestsFailedException: Tests unsuccessful [error] (dfdl-edifact / Test / test) sbt.TestsFailedException: Tests unsuccessful [error] (udf-geoutil / Test / test) sbt.TestsFailedException: Tests unsuccessful [error] (dfdl-nacha / Test / test) sbt.TestsFailedException: Tests unsuccessful [error] (dfdl-link16 / Test / test) sbt.TestsFailedException: Tests unsuccessful [error] (dfdl-examples-hexwords / Test / test) sbt.TestsFailedException: Tests unsuccessful I will investigate why this is. From looking at the diagnostics, one of them at least is due to xmlns="...." changes in expected output vs. actual, and since there was a change there in 3.2.0 I expect that may be a matter of adjusting the test case data. However, there is at least one bug here. As one of the failures is due to an Assert.impossible(....) call executing. On Tue, Nov 2, 2021 at 1:39 PM John Wass <[email protected]> wrote: > Nothing here for 3.2.0. > > On Mon, Nov 1, 2021 at 3:42 PM Interrante, John A (GE Research, US) < > [email protected]> wrote: > > > I checked the Daffodil JIRA to see how many blocker, critical, and major > > issues we have so far: > > > > Blocker issues: 0 > > Critical issues: 1 > > https://issues.apache.org/jira/browse/DAFFODIL-2400 - New SAX > API > > causes performance degradations > > Major issues: 132 > > https://issues.apache.org/jira/browse/DAFFODIL-2574 - Cast error > > when multiplying two unsignedBytes > > and so on - too many to list individually > > > > The critical issue isn't a blocker and in fact hasn't been updated since > > October 2020 (1 year ago). I see Daffodil's release plan in > > > https://cwiki.apache.org/confluence/display/DAFFODIL/Roadmap+for+Upcoming+Releases > > already suggests reducing the number of JIRA issues between 3.2.0 and > 3.3.0 > > which sounds like a good plan. Everything planned for 3.2.0 seems to be > > already checked off. > > > > I looked over the instructions in > > https://cwiki.apache.org/confluence/display/DAFFODIL/Release+Workflow > > carefully and preparing a release candidate looks doable but still a > > time-consuming bit of work. Since we already have a volunteer, I'd > rather > > wait for another release (thanks Mike). > > > > The first step in the Release workflow says to create a [DISCUSS] thread > > and allow time for discussion before creating the release candidate. > I've > > renamed this email's subject to start that formal thread and I'm fine > with > > waiting less than 72 hours if we get responses from everyone we know who > > might be working on anything that they want to release in 3.2.0. I plan > to > > make some more changes and improvements to the Daffodil C code generator > > myself but the changes can go into 3.3.0 since I already build Daffodil > > from source anyway. Is Steve Lawrence or John Wass working on something > > that should make it into 3.2.0? Anyone else? > > > > John > > > > -----Original Message----- > > From: Mike Beckerle <[email protected]> > > Sent: Monday, November 1, 2021 1:44 PM > > To: [email protected] > > Subject: EXT: Are we ready to release 3.2.0 Daffodil ? > > > > I believe 3.2.0 is functionally complete. > > > > Should we prepare a release candidate that we can vote on? > > > > We need someone to volunteer to be release manager. > > > > I am willing to do so, as I've not done this for several releases. > > However, if someone else who hasn't done one would like a chance, I will > > defer to them. > > >
