astefanutti edited a comment on issue #2623: URL: https://github.com/apache/camel-k/issues/2623#issuecomment-928993740
> > You also miss the opportunity to learn new APIs and concepts introduced in newer versions. > > The PRs are created with links to changelog and new commits > > > I fear it would be equivalent to excluding 80% of the project dependencies, which would defeat the purpose of it. > > it is already a win for 20% of the dependencies and does not impact the 80 other percent. > > > I'd also argue that dependency management is too critical for a project like Camel K, that evolves in a fast-moving ecosystem, to be delegated to tools as naive as dependabot. > > I tend to think the exact opposite. Because it is a fast-moving ecosystem, we need to try to follow-up on latest versions and detect incompatibilities even faster than slow-paced projects. This is exactly what we are doing. The issue statement forgets to mention that very point! So it's an issue for a problem that does not really exists, and propose to apply a one-size fits all solution that is less efficient than the current process. For instance, the screenshot of the proposed upgrades is totally inapplicable, because the logic is so naive. On the other hand we did the upgrade with #2655 in less that 24 hours after it became possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
