-
Notifications
You must be signed in to change notification settings - Fork 40
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
2.6 branch #1315
2.6 branch #1315
Conversation
Signed-off-by: Lucas Heitzmann Gabrielli <lucas@flexcompute.com>
The current error message suggests using a function in Trimesh that will be deprecated in March 2024, and using it now results in some weird errors. The alternative suggestion I'm works.
Signed-off-by: Lucas Heitzmann Gabrielli <lucas@flexcompute.com>
PRs that need to be merged only when the release is happening (in order):
|
Just wondering, why would we need to wait until the release? Could we just merge everything into pre/2.6 as soon as available? (or would that update our displayed 2.6.0rc1 docs?) |
So the problem is that the FAQs develop branch is linked to the helpcenter, which would break all links. For notebooks, actually true, I think I had the intention to check that any new notebooks had their links updated before the release. But we could do that in two PRs |
ok, so this will only be an issue for 2.6? (not 2.7+?) |
Yeah exactly, that's why thought to help out organizing the PR order |
No description provided.