(I forgot that there are non-PMC
members on the dev list.)
-Original Message-
From: Steve Lawrence
Sent: Friday, March 18, 2022 4:41 AM
To: dev@daffodil.apache.org
Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
WARNING: This email originated from outside of GE. Please valida
bers in my vote email. Everyone is
welcome to vote, not only PMC members. (I forgot that there are non-PMC
members on the dev list.)
-Original Message-
From: Steve Lawrence
Sent: Friday, March 18, 2022 4:41 AM
To: dev@daffodil.apache.org
Subject: EXT: Re: [DISCUSS] need to release Daff
se notes by reviewing Prepare for Release 3.3.0 by
tuxji · Pull Request #82 · apache/daffodil-site
(github.com)<https://github.com/apache/daffodil-site/pull/82>.
From: Mike Beckerle
Sent: Thursday, March 17, 2022 6:54 AM
To: Interrante, John A (GE Research, US)
Cc: dev@daffodil.apache.o
list of issues, editing the issue numbers to {% jira
%} format, and editing the category titles.
John
-Original Message-
From: Interrante, John A (GE Research, US)
Sent: Thursday, March 17, 2022 10:19 AM
To: mbecke...@apache.org
Cc: dev@daffodil.apache.org
Subject: EXT: [DISCUSS] need to
l-site
(github.com)<https://github.com/apache/daffodil-site/pull/82>.
From: Mike Beckerle
Sent: Thursday, March 17, 2022 6:54 AM
To: Interrante, John A (GE Research, US)
Cc: dev@daffodil.apache.org
Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
WARNING: This email originated fro
t need the rc soon (I won't have time to prepare a rc until Thursday
> evening and it's my first time so it would take more time).
>
> John
>
> -Original Message-
> From: Mike Beckerle
> Sent: Tuesday, March 15, 2022 1:59 PM
> To: dev@daffodil.apache.org
h 15, 2022 1:59 PM
To: dev@daffodil.apache.org
Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
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.
Ok, all the critical issues
gt;>
>>> Agreed. +1 to start the release processes once these are resolved.
>>>
>>> On 3/10/22 6:05 PM, Interrante, John A (GE Research, US) wrote:
>>> > Fixing these 3 tickets seems sufficient to me.
>>> >
>>> > -Origin
-Original Message-
>> > From: Mike Beckerle
>> > Sent: Wednesday, March 9, 2022 6:00 PM
>> > To: dev@daffodil.apache.org
>> > Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
>> >
>> > Once the revert/fix for re
> -Original Message-
> > From: Mike Beckerle
> > Sent: Wednesday, March 9, 2022 6:00 PM
> > To: dev@daffodil.apache.org
> > Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
> >
> > Once the revert/fix for regressions is merged, I think we're
Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
Once the revert/fix for regressions is merged, I think we're down to just these
3 tickets as really critical for Daffodil 3.3.0 release:
DAFFODIL-2652 <https://issues.apache.org/jira/browse/DAFFODIL-2652> - Ability
to
Fixing these 3 tickets seems sufficient to me.
-Original Message-
From: Mike Beckerle
Sent: Wednesday, March 9, 2022 6:00 PM
To: dev@daffodil.apache.org
Subject: EXT: Re: [DISCUSS] need to release Daffodil 3.3.0
Once the revert/fix for regressions is merged, I think we're down to
ctually incorrect in some way that we're
>>> now
>>> > detecting more effectively, that is the right fix.)
>>> >
>>> >
>>> >
>>> > On Tue, Feb 22, 2022 at 11:38 AM Interrante, John A (GE Research, US) <
>>> > john.interra...@ge
cker or urgent issues that must be fixed before
>> >> the next release (only some things I will need to start working on in
>> the C
>> >> backend, "Runtime 2," to handle some more complicated schemas).
>> >>
>> >> How will the roadmap for
(only some things I will need to start working on in
> the C
> >> backend, "Runtime 2," to handle some more complicated schemas).
> >>
> >> How will the roadmap for upcoming releases (
> >>
> https://cwiki.apache.org/confluence/display/DAFFODIL/Roadmap
mas).
How will the roadmap for upcoming releases (
https://cwiki.apache.org/confluence/display/DAFFODIL/Roadmap+for+Upcoming+Releases)
change as a result of 3.3.0 being released asap?
John
-Original Message-
From: Mike Beckerle
Sent: Tuesday, February 22, 2022 10:44 AM
To: dev@daffodi
t; https://cwiki.apache.org/confluence/display/DAFFODIL/Roadmap+for+Upcoming+Releases)
> change as a result of 3.3.0 being released asap?
>
> John
>
> -Original Message-
> From: Mike Beckerle
> Sent: Tuesday, February 22, 2022 10:44 AM
> To: dev@daffodil.apache.org
&
apache.org/confluence/display/DAFFODIL/Roadmap+for+Upcoming+Releases)
change as a result of 3.3.0 being released asap?
John
-Original Message-
From: Mike Beckerle
Sent: Tuesday, February 22, 2022 10:44 AM
To: dev@daffodil.apache.org
Subject: EXT: [DISCUSS] need to release Daffodil 3.3.0
WAR
One issue, which may be in the NITF schema, or may be a daffodil issue is
reported on NITF here:
https://github.com/DFDLSchemas/NITF/issues/15
On Tue, Feb 22, 2022 at 10:43 AM Mike Beckerle wrote:
> A number of people are asking for 3.3.0, with its many bug fixes, to be
> released asap.
>
> Ar
A number of people are asking for 3.3.0, with its many bug fixes, to be
released asap.
Are there any remaining issues that must be fixed before this release?
Otherwise I'd like to suggest we release 3.3.0.
20 matches
Mail list logo
