Re: SC 3.11 from git
[email protected] Wed, 11 Nov 2020 20:51:35 +0000
| Newsgroups | gmane.comp.audio.supercollider.devel |
|---|---|
| Message-ID | <XhXFIpVOP9wQRuqchc7qCMBJJk1PF1ZXZR7jK2gmqARn9kqu1yrOFY-m9GYmg8LR7tBGREf0QV-9fz_2tBfsb2dTV8i960Isw2sfVaAn1e0=@brianlheim.com> |
=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Wednesday, November 11, 2020 1:11 PM, <[email protected]> wrote: > hi all, > > tl;dr if i build develop branch from git i'm on 3.11? as Marcin said, if you build from the tip of develop, you are effectively c= ompiling an "unstable" prerelease build for the next minor version. > > i've tried master and develop, master claims 3.10 on startup and develop > is silent about it, git grep in develop has two hits on 3.11 you probably need to pull from upstream to get the latest updates to the ma= ster branch, then; the latest release is 3.11.1, soon to be 3.11.2. also, e= ach release is tagged in git according to the convention "Version-x.y.z". t= he latest commit to master is *always* tagged this way, because master -- s= oon to be replaced with "main" -- is our stable release branch. we additionally publish source releases of the project for compiling on Lin= ux at https://github.com/supercollider/supercollider/releases (the "...-Sou= rce.tar.bz" artifacts). -Brian _______________________________________________ sc-dev 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-dev/ search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/