-
-
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.8.0 Release #6469
Comments
Hi @nickmcintyre, please let us know if you'd like to merge some of the p5.js Reference documentation pull requests for your SoD project. Hi @Ayush23Dash, please let us know if you need any help in some of the issues related to your GSoC FES project. Thanks! |
#6447 I've submitted a merge request with the required code commits for your review. I believe the changes are ready for merging and could potentially be included before the upcoming releases. |
@davepagurek Should we label #6460 for the 1.8.0 release? |
There are a few known bugs that are present in supplying user-made shaders to For #6216, @RandomGamingDev mentioned on Discord that they likely wouldn't have the time this month to work on it but would pick it up again later, so it's probably best to save that one for the next release. #6397 has had a lot of discussion and #6460 is ready to review based on the discussion up until this point. We can maybe iterate more in future versions, but I think getting at least this first iteration in for the release would help. |
@Qianqianye thanks for including me! I'll open the remaining SoD issues soon and will add them to the 1.8.0 milestone. |
OK I think all the extra WebGL issues I mentioned are resolved! |
Thank you all! p5.js v1.8.0 is just released. We will plan the next release in one month or two. |
Hi @Qianqianye , |
Topic
Hi all, we’d like to release p5.js
1.8.0
in late October. Are there any specific issues we should resolve or any pull requests need to get merged before then?Below are some issues and pull requests we can focus our efforts on before the
1.8.0
release:Please let us know if we should label some other issues to the 1.8.0 Milestone. Thank you!
CC the current p5.js stewards and some active contributors: @limzykenneth @davepagurek @inaridarkfox4231 @GusBusDraws @ShenpaiSharma @asukaminato0721 @aceslowman @aferriss @calebfoss @paulaxisabel @dhowe @Pritam1136 @cosmicbhejafry @SoundaryaKoutharapu @ericnlchen @SarveshLimaye @ChihYungChang @miguellacorte @teragramgius @bsubbaraman @albertomancia @JazerUCSB @apoorva-a98 @richardegil @tedkmburu @mrbrack @TJ723 @angelabelle @shahankhatch @littlejacinthe @perminder-17 @tuminzee @TanviKumar @Zarkv @SkylerW99 @ramya202000 @itsjoopark @BamaCharanChhandogi @Obi-Engine10 @MarceloGoncalves @hannahvy @glopzel @robin-haxx @Gaurav-1306 @bisabi-01 @bayomayo @singshris @jeanetteandrews @hiddenenigma @nhasalajoshi
The text was updated successfully, but these errors were encountered: