-
Notifications
You must be signed in to change notification settings - Fork 381
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 version 0.2.6 (or something else) to address critical bugs #1356
Comments
Hi! Thanks for the inquiry! I'm not sure these issues (except #1302) would be solved on the main branch. so, the next release should be Currently dev time is very low, as it's basically only me submitting patches, reviewing and triaging issues. I'd love to have more help :) |
I'm really looking forward to a new release for #1222 |
|
@tiann I fail to see how that is related, you just need to update the toolchain as explained in the message
|
@Emilgardis Im also waiting desperately for the new release to get "docker_inspect_self_mountinfo" |
I have discovered that bugs reported in the #1298, #1300, #1302, #1307, and #1344 issues are specific to version 0.2.5 of
cross
. It has come to my attention that the build from themain
branch is functioning flawlessly, which is great news.However, considering that users generally prefer the stability of a "release" (or "versioned") build over a development build, it is unfortunate that they are experiencing errors that are only present in version 0.2.5. This puts them in a difficult situation, as they are unable to benefit from the improvements and fixes introduced in the latest version.
To address this issue and ensure a smoother user experience, I suggest releasing version 0.2.6 (or something else) as soon as we could. By doing so, we can provide users with an updated version that resolves the reported bugs and offers enhanced stability. This will not only improve user satisfaction but also enable them to utilize the software without being hindered by known issues.
I kindly request the team's consideration and prompt action in releasing next version to help users overcome these errors and enjoy a more reliable software experience.
The text was updated successfully, but these errors were encountered: