Skip to content

Conversation

@dkarrasch
Copy link
Contributor

The diff looks exactly like it should. This PR backports some minor changes to the pre-1.0 series, at which many packages are still stuck because of old compat restrictions. I'm convinced, however, that most if not all could bump their compat restriction to v1.x. Without that bump, however, all these packages will stop working on Julia v1.10, after JuliaLang/julia#26307 is merged.

Before we merge this, let's wait for a confirmation that we're on the right track.

Copy link
Collaborator

@mateuszbaran mateuszbaran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine to me but I will wait with merging a couple of days to let people comment on this. I think people should just move to StaticArrays.jl at this point, I haven't seen a good reason not to. I guess the packages stuck on StaticArrays.jl 0.12 are just no longer maintained?

@dkarrasch
Copy link
Contributor Author

Perhaps we should include Julia v1.6 in CI on this branch.

@mateuszbaran
Copy link
Collaborator

Yes, sure, adding Julia 1.6 to CI here is a good idea.

@mateuszbaran
Copy link
Collaborator

Hm, it looks like a bit more needs to get backported to make the tests running on newer Julia versions. BTW, I'd still like to keep testing on Julia 1.0 on this branch.

@dkarrasch
Copy link
Contributor Author

dkarrasch commented Mar 28, 2023

Honestly, I think we should just merge and release. The last pre-v1 version of this package has 53 ambiguities, this PR has only 52 (at least locally). Packages that are bound to <v1 of StaticArrays.jl already need to live with those 53 ambiguities on Julia v1.6 (and perhaps beyond). The way how to resolve the ambiguities is to bump the compat restriction. I can adjust the failing test for this branch to have green CI.

@dkarrasch
Copy link
Contributor Author

Boy, independently from the original intention here, there are a lot of tests that need adoption. I'll shout when this is done.

@dkarrasch
Copy link
Contributor Author

Hm, another option could be to release a v0.12.6 with a Julia compat bounded from above by <v1.6... Clearly, the v0.12 series has not been maintained (not even tested) on Julia v1.6+, and several tests fail as they currently stand. One could argue that the pre-v1 series is "broken" on Julia v1.6+, and should therefore not be used. The question then is how to nudge package maintainers to lift their compat for StaticArrays.jl. The test adoptions are a pain!

@mateuszbaran
Copy link
Collaborator

Hm, yes, this doesn't look good.

Hm, another option could be to release a v0.12.6 with a Julia compat bounded from above by <v1.6

As far as I can see, this doesn't solve any problem because it won't un-block changing AbstractTriangular in Julia 1.10+ because those packages couldn't use StaticArrays.jl 0.12.6 with newer versions of Julia.

The question then is how to nudge package maintainers to lift their compat for StaticArrays.jl.

Probably just opening issues on github or writing e-mails to maintainers? This would really be the best solution but I doubt all of these packages are still actively maintained.

@dkarrasch
Copy link
Contributor Author

Boy, this is so broken (in terms of functionality, it can still be loaded though)... and apparently, the packages that are still stuck on pre-v1 don't need any of the broken functionality, so they don't see it. I think this can be merged and released now.

@mateuszbaran
Copy link
Collaborator

That's indeed quite a few broken things. Let's release it though and see what happens.

@mateuszbaran mateuszbaran merged commit 3e50fd8 into JuliaArrays:release-0.12 Apr 11, 2023
@dkarrasch dkarrasch deleted the dk/backport-triangular branch April 11, 2023 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants