@mattip

Should we have any overlap and release both wheels for 2.1 or can we not release a 1_2 wheel with no prior announcement?

It would have to be added as a matrix. I'm not sure of the compatibility of 1_2. https://discuss.python.org/t/wheels-for-musl-alpine/7084/22?page=2 might be useful.

1_1 wheels should run on 1_2, I don't think pip will install 1_2 wheels on 1_1. Although 1_1 is 2.5 % of the current downloads vs. 97.5% for 1_2, 2.5% is still a lot of NumPy users. Are we OK not releasing NumPy2.1 for that small group?

Ok. How about we use 1_1 for the next release, but 1_2 following that, and make an announcement on the ML?

How about we use 1_1 for the next release, but 1_2 following that, and make an announcement on the ML?

That sounds like a good plan to me. Second-best plan is to just drop 1_1 now. Building for both doesn't sound right, too much effort/builds for little gain.

Should probably change this line as well, so we are testing on 1_2

Send intention email to ML on 2024_08_11

Cross-linking to the mailing list discussion.

I had a look at the repo and couldn't find any more places to make a change from 1_1 to 1_2. Is there an appropriate place in the documentation to mention this?

Maybe add a release note?

@andyfaff A release note would be good, then we can put this in.

Can you remind me where I make those?

where I make those?

doc/release/upcoming_changes. There are already some release notes there that you can use to see how to do it.

@charris, I've made that release note.

Thanks @andyfaff