You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On behalf of Redocly, maintainers of the Redoc open source project, I'm here to share our plans for the coming months. You might already know that we offer API reference documentation as a service; we're working on launching a new version of that on our cloud platform [1]. Once it's live and we're happy with it, we'll be releasing it as the next version of open source Redoc.
We want to be transparent with you that we're excited to have something new coming up, but that this does mean we'll be hitting pause on development of the current version of Redoc. We'll still be reviewing and merging pull requests, and responding to issues and questions as always. You'll notice us closing issues as "not planned", not because they're not great ideas, but because we won't be building those features for the current version and we want to be upfront about what's happening and why.
Please be patient with us through this transition, Redoc is close to our hearts as it is to yours, and we're excited to bring you something new!
For anyone interested, our product newsletter will keep you up to date regarding all the product releases.
The text was updated successfully, but these errors were encountered:
On behalf of Redocly, maintainers of the Redoc open source project, I'm here to share our plans for the coming months. You might already know that we offer API reference documentation as a service; we're working on launching a new version of that on our cloud platform [1]. Once it's live and we're happy with it, we'll be releasing it as the next version of open source Redoc.
We want to be transparent with you that we're excited to have something new coming up, but that this does mean we'll be hitting pause on development of the current version of Redoc. We'll still be reviewing and merging pull requests, and responding to issues and questions as always. You'll notice us closing issues as "not planned", not because they're not great ideas, but because we won't be building those features for the current version and we want to be upfront about what's happening and why.
Please be patient with us through this transition, Redoc is close to our hearts as it is to yours, and we're excited to bring you something new!
The text was updated successfully, but these errors were encountered: