-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
sage: 8.3 -> 8.4 #44527
sage: 8.3 -> 8.4 #44527
Conversation
Turns out the filename is important. It should be `cblas`, not `openblas-cblas`. (cherry picked from commit 408eacb)
I got a GitHub notification that you (@timokau) have pushed 0 commits. Was it a rebase? |
I actually did push some commits (updating to beta3, merging master, cherry-picking the openblas fix from staging, updating to beta4). I did rebase but only locally with stuff I didn't push yet (no force-push). I don't know what confused github. I usually don't get any notifications at all if a PR gets updated by force-push. |
So, a release has happenned? |
Yes, I just got a bit sick and thus didn't do a final review & merge yet. Do you think the changes should be squashed? Thats how I did it the previous release but preserving the in-between releases might not hurt either when bisecting some issue. |
No idea re:squashing, given that most intermediate commits are plain bumps… I guess it is you who would bisect Sage RCs anyway |
The RCs yes, but the betas usually also remove some patches that were included upstream or something. I think preserving that history might be valuable, but it would also "pollute" commit history a bit. |
Given that every commit is a working state, I guess it is not making anything worse compared to the status quo (we will have a lot of merged small branches until the entire model of interaction with the non-committer contributors is different). So please do not underestimate the importance of your convenience in maintaining Sage. (Personally, I do value keeping the true history of changes; I also find use of Git usually suboptimal for that goal) |
I agree. Thanks for your opinion :) All but two of the nix specific patches are upstreamed now 🎉 |
Oops should've removed the WIP label first. |
Motivation for this change
There ain't no rest for the wicked, sage updates don't grow on trees...
Shortly after the 8.3 update, the first 8.4 beta is already released.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)