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
Yes, the master branch is kept stable, building and passing tests at all times (and checked for all platforms by the CI), so you can rely on it.
As for the release, I'm well aware that not having a tagged release for so long is bad (makes packaging hard, etc.), but unfortunately since the last one many large-scale features and reworks were started and aren't finished yet. I don't want to tag something that would have partially unfinished APIs or feature sets because then I would have to keep backwards compatibility with those. Fortunately it's all slowly coming together, so there will be a release. The pending tasks are tracked in mosra/magnum#453 and the corresponding milestone in all repos. But until that happens you can safely rely on master.
Are there plans to create a new release that includes a06a17c or can every master commit be considered as release ready?
The text was updated successfully, but these errors were encountered: