-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
1.7.0 Release #6215
Comments
This one is a bug only on the main branch currently, so we might want to try to fix it before releasing to avoid a regression (although it means some errors are just less helpful, so we could also decide it's not critical): #6172 One other thought: once we have fixes in for everything here, do you think it's worth it to make a beta release? This is mostly motivated by the fact that I found a bug (#6200) by trying to make a sketch off of a main branch build as opposed to the more focused testing I'd normally do on a custom build. If we make an easier way to test the changes, so you don't have to build and upload p5, maybe we can catch a few more things? |
I would like to implement a vector slerp function and a function that performs camera interpolation. I don't know if I'll make it in time... slerp is a function that does a spherical linear interpolation of two vectors. 2023-06-18.11-11-34.mp4You can use the camera interpolation function to smoothly return a camera moved by orbitControl to its initial state, for example. 2023-06-18.11-11-03.mp4 |
|
I'm going to be away for two weeks starting Friday so I'll leave some updates here if other progress is made:
|
We are planning to do the 1.7.0 release at the week of July 10 and the next release within 1-2 months (in August or September). Wondering if there're any PRs from this year's GSoC p5.js contributors that should get merged for 1.7.0 release?
|
Hi,
Would be added |
The image-based lighting project isn't aiming to have code in for this release (maybe the next one though!) |
@Qianqianye, I'm sorry if this is already taken care of or is a redundant answer. FES got this bug fix by @Ayush23Dash that has been merged that can be included in the 1.7.0 release: |
I'm planning on having my first round of a11y-fixing PRs sent in by late next week. My contributions can wait until the next version update, just in case there's any blips or revisions needed. |
After talking with @wong-justin (Shader-Based Filters project), we don't believe that the contributions will quite be ready for 1.7.0, but would like to work towards the goal of the next release. |
Thank you all! v1.7.0 is just released. We will plan the next release in one month or two. |
Topic
Hi all, we’d like to release p5.js
1.7.0
in July. Are there any specific issues we should resolve or any pull requests need to get merged before then?Below are some issues we can focus our efforts on before the
1.7.0
release:Please let us know if we should label some other issues to the 1.7.0 Milestone. Thank you!
CC @limzykenneth @davepagurek @outofambit @raclim @aferriss @almchung @nickmcintyre @wuyudi @inaridarkfox4231
The text was updated successfully, but these errors were encountered: