knockknock10 commented on PR #6917: URL: https://github.com/apache/camel-k/pull/6917#issuecomment-6720632743
> I think we should keep the design document generic. We should describe the problem statement and then shortly explain how we can do the development with a low level design explaination. We should not include too many details around the yaml, java or xml and just explain how generically we should do the work (low level design). > > Also let's avoid timing specific explanation (ie, first implementation) as the goal of this document is to illustrate a design which can be tackled in several steps or one off. It is not the scope of this document to explain how to do it. Thanks for the feedback. I've updated the proposal to keep it generic, focusing on the problem statement and low-level design rather than source-format-specific implementation details. I've also removed the implementation sequencing language, aligned the PR description with the document, and added the dated implementation tracker with the current progress and review status of #6942. Please let me know if anything else needs adjustment. -- 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]
