[
https://issues.apache.org/jira/browse/CAMEL-22357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18015152#comment-18015152
]
Claus Ibsen commented on CAMEL-22357:
-------------------------------------
Yes if this is something that is quick and easy to do - I dont want the project
to be slowed down or hold back due to red tape.
So if we know that there is a rule for this change in the upgrade guide. Then
sure it's nice to add a note about that. But we also risk that those guides are
then half validated and you cant 100% rely on this fact.
I think on top of this then we should make more attention about this tool so
end users can know about it and use it more.
> Mark topics (from upgrade guide), which are covered by update tool
> ------------------------------------------------------------------
>
> Key: CAMEL-22357
> URL: https://issues.apache.org/jira/browse/CAMEL-22357
> Project: Camel
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 4.14.0
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Priority: Minor
>
> I think that it would be nice (and useful for users) to share, which parts of
> the migration guide are covered by automation ([migration
> tool|https://github.com/apache/camel-upgrade-recipes/])
> From my POV the nice solution would be to add some kind of information into
> camel guide (i.e. [Upgrading Camel 4.13 to
> 4.14|https://camel.apache.org/manual/camel-4x-upgrade-guide-4_14.html#_upgrading_camel_4_13_to_4_14])
> Let say to add "labels" for each chapter/topic:
> * `covered by mig. tool`
> * `partially covered by mig. tool`
> * `NOT covered by mig. tool`
> And add link + description for the migration tool into the footer of the
> migration guide page.
> [~davsclaus] What do you think about it?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
