LuboTerifaj commented on PR #648:
URL: 
https://github.com/apache/incubator-kie-kogito-docs/pull/648#issuecomment-2173989874

   Hello @domhanak , thank you for merging.
   
   I tried to provide as much information as possible. The updates for kn 
plugin are indeed tracked. How it is being tracked is a different problem. I am 
not sure what question I didn't answer. So let's recap.
   
   To your questions:
   
   - "Is this updated to include the latest kn cli updates and how it will be 
when we release apache 10.0.0 kn workflow?"
     - Answered in 
https://github.com/apache/incubator-kie-kogito-docs/pull/648#issuecomment-2160500648
   - "If you do not know the details, how did you validate the bits that use 
it?"
     - Validating the bits using main branch was not the goal of the 
documentation review. I did validate the latest released bits (0.32.0). We 
should not advise users to build the plugin by themselves from main.
   - "Also latest release means 0.32.0?"
     - Yes.
   - "So does the current state mean main branch please?"
     - No. The current state means using the latest release (0.32.0).
   
   Any changes made to main that could affect the documentation should be 
reported to the documentation team by the issue assignee. In this way we ensure 
the changes will get to the documentation.
   Updating kn workflow plugin set-up in the documentation is currently tracked 
by https://issues.redhat.com/browse/KOGITO-9989. I understand the KOGITO jira 
is deprecated, but it's not so far in the past we were using that jira for the 
issues and I don't think we already migrated all the issues to Apache github 
issues. In addition, some community members may forgot or not be aware of it, 
and report the issue in deprecated KOGITO jira. Anyway, I reported the issue 
also here to properly track it in Apache community:
   
   - https://github.com/apache/incubator-kie-kogito-docs/issues/661
   
   I hope this clarifies your concerns/questions.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to