SuperCollider 3.7 prerelease

SuperCollider 3.7

SuperCollider 3.7.0 prerelease builds are now available. These will be released regularly until the application is considered stable and a release candidate is declared.

This release has been in continuous use during it’s development, so it is considered stable enough for day-to-day use. It should be backwards compatibly with any code from 3.6.6.

3.7 can coexist with 3.6.6 and other SC versions. We recommend you backup your sc_ide_conf.yaml - settings from 3.6.6 should be forwards compatible, but using a 3.7 settings file in 3.6.6 is not supported (though it may partially work). This can be found in the user support folder (File > ‘Open user support directory’).

How can I help?

Report bugs

Please run existing SC projects and report any significant failures or unexpected behaviors. This is also a chance to report long-standing issues that have not been addressed in 3.7.

If you have access to uncommon hardware setups, or OS distributions, your testing is especially important! Please take a moment to smoke-test with your specialized linux distro or custom HID-based device and report back!

Help triage bugs

SuperCollider currently has 345 open issues, many of which are years old - as we beta test 3.7, we expect that number to increase. We need help dealing with new bugs, and sorting through old bugs and features (many of which may already be fixed). This is also a good chance to advocate for getting your (least) favorite bugs fixed. Please read the bug triage guidelines and ask on sc-users or sc-dev if you would like to contribute to this process.

Fix an easy bug

Simple-to-fix bugs and documentation / string issues are marked with the low hanging fruit label in the issues database. If you haven’t contributed a pull request to SuperCollider before, or need an excuse to build locally, these are a good place to start.

Write / review documentation

SuperCollider’s documentation is always a work in progress. Classes in need of documentation can be found in the Help docklet, via Browse > Undocumented Classes). Or, walk through your own code, look up help on the Classes and Methods you’re using, and document the ones that don’t currently have documentation.

alpha1

Windows builds are still in progress. Much progress has been made, but a few core issues have to be fixed before a working alpha build can be made available.