Organizing a 3.14 release for the symposium?

Development
1

Quoting myself from 3.14 release · Issue #6579 · supercollider/supercollider · GitHub

SuperCollider 3.13.0 was released in February of 2023 and since then we had some great additions, fixes and improvements which are probably useful to distribute them to a wider audience through an official release.

Having the SuperCollider symposium on 13-15 March 2025 labelled The Future of SuperCollider, I’d propose to use this event as an opportunity to release the next major version, which would be 3.14.0 :slight_smile:

Currently I consider the feedback on the GH issue too sparse in order to give the endeavor a go as bundling a release can only be a group effort. As the timeslot towards the symposium is getting smaller, I thought about asking once more a broader audience here before deciding to let the opportunity pass and push the release to a later date.

On a more general note: If you want to contribute to SC you can have a look at the development board at SuperCollider development · GitHub about what needs to be done on existing PRs. I always try to keep the board up-to-date.

We are also always in need of people who test and review features! Do not hesitate to simply start commenting on PRs, see Reviewing proposed changes in a pull request - GitHub Docs and Reviewer instructions · supercollider/supercollider Wiki · GitHub on the how-tos of the procedure. Even if you are not in the reviewer group yet, you can already comment and test PRs.

2 Likes
2

Agreed!

I wonder how we, as a group, feel about relaxing some of the dev and review procedures. In the late 2010s, it was certainly necessary to tighten down procedures because of code quality problems and insufficient testing of PRs. (I remember 2015-2016 era SC…) But I also feel like the move to “professionalize” SC dev ended up causing a number of contributors to drop out, and we’re now feeling the pinch from that. It is, after all, a volunteer effort; I felt that there may have been some misunderstanding in the early 2020s about what volunteers are.

Since the only SC release in the last year(?) fixed one bug for one OS (IIRC), it seems pretty obvious that we need to do something concrete to encourage participation. Simplifying procedures and lowering the entry barrier somewhat could help (and it might bring it more within reach for me to be more involved again, and I’d hope for others as well).

hjh

3

Re getting more people involved in prs, I think the supercollider guide for contributing on GitHub is far to big.

There are 65 pages…

While rules and procedures are useful, these could be prioritised more, and when/if there are any major deviations,
they could be pointed out after the fact, as right now, the documentation reads like you must understand all this before you comment on a PR.

1 Like