[ 
https://issues.apache.org/jira/browse/DAFFODIL-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568125#comment-17568125
 ] 

Steve Lawrence commented on DAFFODIL-2712:
------------------------------------------

Some updates in the past have required a considerable amount of work (I recall 
ICU had some issues a long time ago and the updates weren't trivial). It would 
be best to know about those issues and allow time for testing new updates 
sooner rather than right before a release.

This also hasn't been a significant issue with Daffodil, IMO. The real issues 
with excessive PRs is with daffodil-vscode, which had a lot of dependencies far 
behind. I'm hoping that once we get those all up to date updates will be more 
spread out.

I think it's important that we keep dependencies updated, and it's much easier 
to do that with a bot checking for updates than some other manual process. If 
it's not automated to some degree, I don't' think it's going to get done.

Maybe we just make it run less frequently like once every some number of weeks.

> Scala Steward no longer runs on Daffodil repo
> ---------------------------------------------
>
>                 Key: DAFFODIL-2712
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2712
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Steve Lawrence
>            Priority: Major
>
> The Scala Steward Org instance was shutdown in June. The recommended way to 
> create PR's for dependency updates is now using the Scala Steward github 
> action. This was added for the daffodil-vscode repo here:
> https://github.com/apache/daffodil-vscode/pull/199/files
> We should do something similar for the daffodil repo.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to