Re: [DISCUSS] Release Daffodil 3.7.0

[Steve Lawrence]

Sounds great! Let me know if I can help with any of the steps.

Also, since the DISCUSS thread was started two more PRs have been opened:

https://github.com/apache/daffodil/pull/1190

https://github.com/apache/daffodil/pull/1189

I think these are worth getting into the 3.7.0 release. No other changes have 
been mentioned, so once those get another +1 and are merged I think we are good 
to start the release process.


On 2024-03-25 11:19 AM, Katlic, Peter (GE Aerospace, US) wrote:

I am interested in getting experience with the release process and volunteer to 
be the release manager for version 3.7.0.

Peter

On 3/21/24, 11:23 AM, "Mike Beckerle" mailto:mbecke...@apache.org>> wrote:


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.


If we can get 1065 (diagnostic file URLs fix) into the release that would
be great. It's worth waiting a day or two for this.


I think the layer changes should go into 3.8.0, which could follow fairly
closely behind 3.7.0 time-line wise, but I'd suggest it is the only change
in that release perhaps since it is a breaking change for anyone using the
layers-extension API, which is an unofficial API, so not really supported,
but still some people (at my employer Owl anyway) are using it.


3.7.0 has some real performance improvements, and while we still have a
ways to go on that front, I think these are significant and we should get
them into people's hands.


It also has the changes to support the Apache Drill integration, which we
need released so that work can continue.








On Wed, Mar 20, 2024 at 9:06 AM Steve Lawrence mailto:slawre...@apache.org>> wrote:



It's about that time again for a release and there are a number of good
bug
fixes and performance improvements that we should get in the hands of
users.

We have two open PRs that seem to have active development:

* #1065 De-personalize Diagnostic File URLs in Compiled Schemas

I think this is very close and can probably be merged in the next day or
so,
unless there are any hesitations about changes to diagnostic paths
breaking
anything, in which case we could push it to the next release to allow more
testing.

* #1187 4th (and final) cut of New Layer API & Improved Implementation

This is a pretty large change to the layer API. I think based on
discussions the
consensus is to push it to the next release since it's a fairly large
change
this close to release.

Any thoughts on these changes or does anyone have additional changes they
are
looking to get in?

We also need a release manager. I'm happy to do it, but it might be good
to have
someone else do it so others get experience with the process. It's pretty
thoroughly documented here:

https://cwiki.apache.org/confluence/display/DAFFODIL/Release+Workflow 

Re: [DISCUSS] Release Daffodil 3.7.0

[Katlic, Peter (GE Aerospace, US)]

I am interested in getting experience with the release process and volunteer to 
be the release manager for version 3.7.0.

Peter

On 3/21/24, 11:23 AM, "Mike Beckerle" mailto:mbecke...@apache.org>> wrote:


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.


If we can get 1065 (diagnostic file URLs fix) into the release that would
be great. It's worth waiting a day or two for this.


I think the layer changes should go into 3.8.0, which could follow fairly
closely behind 3.7.0 time-line wise, but I'd suggest it is the only change
in that release perhaps since it is a breaking change for anyone using the
layers-extension API, which is an unofficial API, so not really supported,
but still some people (at my employer Owl anyway) are using it.


3.7.0 has some real performance improvements, and while we still have a
ways to go on that front, I think these are significant and we should get
them into people's hands.


It also has the changes to support the Apache Drill integration, which we
need released so that work can continue.








On Wed, Mar 20, 2024 at 9:06 AM Steve Lawrence mailto:slawre...@apache.org>> wrote:


> It's about that time again for a release and there are a number of good
> bug
> fixes and performance improvements that we should get in the hands of
> users.
>
> We have two open PRs that seem to have active development:
>
> * #1065 De-personalize Diagnostic File URLs in Compiled Schemas
>
> I think this is very close and can probably be merged in the next day or
> so,
> unless there are any hesitations about changes to diagnostic paths
> breaking
> anything, in which case we could push it to the next release to allow more
> testing.
>
> * #1187 4th (and final) cut of New Layer API & Improved Implementation
>
> This is a pretty large change to the layer API. I think based on
> discussions the
> consensus is to push it to the next release since it's a fairly large
> change
> this close to release.
>
> Any thoughts on these changes or does anyone have additional changes they
> are
> looking to get in?
>
> We also need a release manager. I'm happy to do it, but it might be good
> to have
> someone else do it so others get experience with the process. It's pretty
> thoroughly documented here:
>
> https://cwiki.apache.org/confluence/display/DAFFODIL/Release+Workflow 
> 
>
>
>

Re: [DISCUSS] Release Daffodil 3.7.0

[Mike Beckerle]

If we can get 1065 (diagnostic file URLs fix) into the release that would
be great. It's worth waiting a day or two for this.

I think the layer changes should go into 3.8.0, which could follow fairly
closely behind 3.7.0 time-line wise,  but I'd suggest it is the only change
in that release perhaps since it is a breaking change for anyone using the
layers-extension API, which is an unofficial API, so not really supported,
but still some people (at my employer Owl anyway) are using it.

3.7.0 has some real performance improvements, and while we still have a
ways to go on that front, I think these are significant and we should get
them into people's hands.

It also has the changes to support the Apache Drill integration, which we
need released so that work can continue.




On Wed, Mar 20, 2024 at 9:06 AM Steve Lawrence  wrote:

> It's about that time again for a release and there are a number of good
> bug
> fixes and performance improvements that we should get in the hands of
> users.
>
> We have two open PRs that seem to have active development:
>
> * #1065 De-personalize Diagnostic File URLs in Compiled Schemas
>
> I think this is very close and can probably be merged in the next day or
> so,
> unless there are any hesitations about changes to diagnostic paths
> breaking
> anything, in which case we could push it to the next release to allow more
> testing.
>
> * #1187 4th (and final) cut of New Layer API & Improved Implementation
>
> This is a pretty large change to the layer API. I think based on
> discussions the
> consensus is to push it to the next release since it's a fairly large
> change
> this close to release.
>
> Any thoughts on these changes or does anyone have additional changes they
> are
> looking to get in?
>
> We also need a release manager. I'm happy to do it, but it might be good
> to have
> someone else do it so others get experience with the process. It's pretty
> thoroughly documented here:
>
> https://cwiki.apache.org/confluence/display/DAFFODIL/Release+Workflow
>
>
>