[
https://issues.apache.org/jira/browse/CAMEL-20959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865468#comment-17865468
]
Claus Ibsen commented on CAMEL-20959:
-------------------------------------
Maybe we can do the first release as 0.x to give us the time to make sure it
becomes correct and as needed. Then after that we can find out if it should be
its own version or follow the camel releases like most all other projects
> 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)
