New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release of 1.0 #165
Comments
Oh wow! This is big. Regarding the fist point, if we keep CMake does it mean that we have to keep it forever? It's not an API-related thing, so I don't know how strict the rules are here. |
No, that's just infrastructure. We can drop it any time but it would be good time instead of keeping it around forever. Although we should really check if someone is not able to use meson/ninja. |
Wait a second, what means 1.0 for you? Tomas was just asking if compiling via |
Ahhh, I see.. Well, I have removed old ufo-core and installed this release using cmake. And it does not work. So I rolled back to April release and it works as it should again. Do I have to reinstall all dependents each time I update core? I had no clue about existence of that meson system, but I will give it a try of course. Cheers, |
That line should be enough, can you replicate the issue @tfarago? |
Hola, let me try to update all modules to the latest versions, I'm pretty sure the problem will disappear. |
This is a meta issue discussing things necessary for the release of version 1.0 that does not allow any API removal or backwards-incompatible change. Of course all tickets marked with a milestone 1.0 should be fixed but there are a few things worth discussing:
The text was updated successfully, but these errors were encountered: