[
https://issues.apache.org/jira/browse/CAMEL-20959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865371#comment-17865371
]
Claus Ibsen commented on CAMEL-20959:
-------------------------------------
No its not on a patch level, only X.Y
So X.Y means that the recipies can go up to X.Y release, ie 4.7
The .Z does not matter. If the recipies needs a fix release then they do 4.7.1
4.7.2 and so on.
So if a user wants to upgrade to Camel 4.7, they grab the latest recipie
release that are 4.7.x based. Or a higher like 4.8.
Forget about Quarkus - this is ASF and our projects should be ASF based.
> Camel-upgrade-recipes: next steps (to enable releasing)
> -------------------------------------------------------
>
> Key: CAMEL-20959
> URL: https://issues.apache.org/jira/browse/CAMEL-20959
> Project: Camel
> Issue Type: Task
> Components: upgrade-recipes
> Reporter: Jiri Ondrusek
> Priority: Major
> Fix For: 4.x
>
>
> TBH I'm not sure what has to be done next.
> [Here|https://github.com/apache/camel-upgrade-recipes/pull/1] is the initial
> commit for the camel-upgrade-recipes repo.
> I think that we should release this library when this commit is merged.
> Why?
> Once released, I can update draft
> [PR|https://github.com/quarkusio/quarkus-updates/pull/177] for
> quarkus-updates project and leverage the camel-upgrade-recipes dependency.
> With some guiding from someone I can try to achieve some of the task.
> (It would be nice to have component in jira, which would represent
> upgrade-recipes.
> The affects version/fix version does not make sense in the camel project, as
> the versioning might be different)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
