RFC: Improve SuperCollider versioning for non-release builds
[email protected] Sun, 28 Mar 2021 10:27:16 -0700
| Newsgroups | gmane.comp.audio.supercollider.user,gmane.comp.audio.supercollider.devel |
|---|---|
| Message-ID | <CAEBNZeAVyC3mdfZO91svVuHdDm3S7PgPX16r6fHsj0y2zPMPVw@mail.gmail.com> |
--000000000000adf59705be9c149c Content-Type: text/plain; charset="UTF-8" A new RFC (request for comment) has been opened here: https://github.com/supercollider/rfcs/pull/16 Please visit the above link for discussion. Summary: I'd like to propose introducing finer granularity in SuperCollider versioning. --000000000000adf59705be9c149c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">A new RFC (request for comment) has been opened here:<br><= br><a href=3D"https://github.com/supercollider/rfcs/pull/16">https://github= .com/supercollider/rfcs/pull/16</a><br><br>Please visit the above link for = discussion.<br><br>Summary: I'd like to propose introducing finer granu= larity in SuperCollider versioning.<br></div> --000000000000adf59705be9c149c-- _______________________________________________ sc-users mailing list info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx archive: http://www.listarc.bham.ac.uk/marchives/sc-users/ search: http://www.listarc.bham.ac.uk/lists/sc-users/search/