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
THIS IS A PRERELEASE! Qodot is still fixing some bugs to make it fully production ready. Most features should work to build basic maps and entities.
Don't forget, we have official docs! See https://qodotplugin.github.io/ for more information, and don't hesitate to request missing information in our issues or on our Discord.
Notably still broken about Qodot 2023.1-prerelease :
A huge thanks to everyone who contributed, commented, provided bug reports and reproduction projects, and gave their opinion about approaches and fixes! ♥
The version number
I've brought up changing from 2.1 to an annual version number multiple times and nobody's been able to stop me yet. So for the time being, version number is annual instead of purely semantic now. I want the use of annual versioning as a way to encourage more releases to be made, at least more than once a year. With new fixes on the horizon there should be another release not too long before now. Thoughts on this change are also welcome.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
THIS IS A PRERELEASE! Qodot is still fixing some bugs to make it fully production ready. Most features should work to build basic maps and entities.
Don't forget, we have official docs! See https://qodotplugin.github.io/ for more information, and don't hesitate to request missing information in our issues or on our Discord.
Notably still broken about Qodot 2023.1-prerelease :
Changelog
A huge thanks to everyone who contributed, commented, provided bug reports and reproduction projects, and gave their opinion about approaches and fixes! ♥
The version number
I've brought up changing from 2.1 to an annual version number multiple times and nobody's been able to stop me yet. So for the time being, version number is annual instead of purely semantic now. I want the use of annual versioning as a way to encourage more releases to be made, at least more than once a year. With new fixes on the horizon there should be another release not too long before now. Thoughts on this change are also welcome.
This discussion was created from the release 2023.1-prerelease.
Beta Was this translation helpful? Give feedback.
All reactions