Inquiry About Circuit API Stability and Future Plans #1135
-
|
Hello Circuit Team and Community, I am writing to inquire about the current status and future plans regarding the stability of the Circuit framework. My team is considering Circuit for an upcoming project, but we have some concerns regarding its stability. As you know, the decision to integrate a specific framework into a large-scale project, especially in corporate environments, is heavily influenced by the framework's stability and long-term support. In this context, could you please provide some insights on the following: Current Status: Is the Circuit API currently considered stable for production use, or is it still in a developmental or experimental phase? Roadmap and Future Plans: Are there any plans or timelines in place for declaring the API stable? If so, could you share some details about these plans? Support and Maintenance: In the event of API stabilization, what kind of support and maintenance can we expect? Are there long-term commitments in this regard? Understanding these aspects is crucial for us to make an informed decision. We are enthusiastic about the potential of using Circuit in our project, but we need to ensure that it aligns with our requirements for stability and ongoing support. Thank you for your time and assistance. Looking forward to your response. Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Per our docs, the API is subject to change for now but circuit itself is safe for production use. As this is a free and open source project, we don't offer SLAs or anything like that. It's not a product :). We try to release quickly, especially when bugs are found and fixed on main. We are committed to it at least for as long as we use it in Slack, which hopefully isn't going anywhere anytime soon. |
Beta Was this translation helpful? Give feedback.
-
|
As we shift our project towards a framework emphasizing clean architecture and enhanced presentation layer management, Circuit emerges as a top candidate. However, its current 'unstable' label is a significant concern for our decision-makers. Could you provide a clearer timeline or criteria for when Circuit will be considered stable? This information is crucial to assure our management of its reliability for long-term use. I also looking forward to contributing to Circuit's development as we integrate it into our project. |
Beta Was this translation helpful? Give feedback.
Per our docs, the API is subject to change for now but circuit itself is safe for production use.
As this is a free and open source project, we don't offer SLAs or anything like that. It's not a product :). We try to release quickly, especially when bugs are found and fixed on main. We are committed to it at least for as long as we use it in Slack, which hopefully isn't going anywhere anytime soon.