Release 14.0.0 #1196
Release 14.0.0 #1196
Conversation
|
@JohanMabille not to be merged, just to get the ball rolling. The changelog was dense so I started grouping it by themes. Also major release because there's an API break |
serge-sans-paille
force-pushed
the
release/14.0.0
branch
2 times, most recently
from
5eceff2 to
6f9d0d0
Compare
|
@serge-sans-paille there are two more improvements to
I can possibly have that within a week. Would that work? I also have an idea for improving some specific cases on |
|
THe initial "plan" was to release mid November, but we didn't fix any date, so I think releasing in one week is fine. |
|
On Mon, Nov 10, 2025 at 11:00:36AM -0800, Antoine Prouvost wrote:
●AntoinePrv left a comment [1](xtensor-stack/xsimd#1196)
***@***.*** there are two more improvements to swizzle that I would
like to get in if possible.
• [3]GH-1197 for 8/16 bits (WIP need to fix the errors);
• I have further improvement to the general case for batch_constant;
I also have an idea for improving some specific cases on batch_constant but
it's a longer shot (possibly very hard under C++11).
Sure, I'll review those.
|
|
I am also trying to get the masked_api done asap. I am just busy with deadlines at the moment. |
serge-sans-paille
force-pushed
the
release/14.0.0
branch
from
6f9d0d0 to
e62a53d
Compare
|
@serge-sans-paille last thing before the release, I think we should investigate the issue I mentioned in below. |
|
I was travelling last week. I just got back I will try to have a look today. |
|
Thanks a lot! |
|
Everything except #1226 has been merged, we're getting close! |
serge-sans-paille
force-pushed
the
release/14.0.0
branch
3 times, most recently
from
80c0b54 to
c752fd2
Compare
Contributors: - Alfredo Tupone - Antoine Prouvost - Chris Lu - Clément Garnier - emrys53 - Johan Mabille - liangbin - Marco Barbone - Marian Klymov - Markus Wick - serge-sans-paille - Sylvain Corlay - Warren Weckesser
serge-sans-paille
force-pushed
the
release/14.0.0
branch
from
c752fd2 to
311942e
Compare
|
@JohanMabille I've updated the contributor list (in the commit message) and the Changelog with the latest commit, I think we're good to go. Do you want to do the release, or Should i handle this? It's fine for me to do this in ~4h |
|
I'm fine with both options, but I won't be able to do it before tomorrow morning.If you do it, can you squash and merge instead of merging (or directly push the commit on master but I think it's equivalent). Also we use annotated tags for release in the stack (but I can't remember why ^^). |
ok, I leave it to you then, don't want to mess up with your workflow ;-) |
|
Release done by cherry-picking the commit and pushing it to master, closing this one. |
Contributors: