davsclaus commented on issue #1267:
URL: 
https://github.com/apache/camel-kamelets/issues/1267#issuecomment-1423894541

   The 3 values today are also what other projects use such as Quarkus.
   I would keep that as-is.
   
   What we could do is to add a 2nd label/enum/note. Where a kamelet can be 
marked as "common", "advanced",  "development", ...
   
   You can have a stable component but it can be advanced / special. 
   
   I dont think we should label stuff as "ready for prod" that is end user that 
decide what to use. But for prod you would favour using "Stable" kamelets and 
maybe in some cases "Preview" for newly added kamelets.
   
   


-- 
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: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to