|

»

»

»

Supercollider - Dev

3.2.something release

View: New views

4 Messages — Rating Filter: Alert me

	3.2.something release by nescivi :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hiho, as this came up... I think it could be a good idea to aim for a 3.2.something release for the end of August... that way anyone who teaches SC in the upcoming academic year, can point students to that release... There have been a number of improvements since 3.2 which make it worthwhile... (from my side: some late fixes for Linux (inclusion of scvim!), some GeneralHID stuff, etc...) If we aim a release for end of August, we have some time till then to finalise and test anything we still want to fix... What do you think? sincerely, Marije _______________________________________________ sc-dev mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/ search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
	Re: 3.2.something release by Josh Parmenter :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I like this idea... except that I would say shoot for end of July (since I know that, at least for me, that is when I have to have software ready for lab computers). Josh On Jun 30, 2008, at 8:46 AM, nescivi wrote: > Hiho, > > as this came up... > I think it could be a good idea to aim for a 3.2.something release > for the end > of August... > > that way anyone who teaches SC in the upcoming academic year, can > point > students to that release... > > There have been a number of improvements since 3.2 which make it > worthwhile... > (from my side: some late fixes for Linux (inclusion of scvim!), some > GeneralHID stuff, etc...) > > If we aim a release for end of August, we have some time till then > to finalise > and test anything we still want to fix... > > What do you think? > > sincerely, > Marije > > _______________________________________________ > sc-dev mailing list > > > info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 > archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/ > search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/ ****************************************** /* Joshua D. Parmenter http://www.realizedsound.net/josh/ “Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono */ _______________________________________________ sc-dev mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/ search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
	Re: 3.2.something release by felix-38 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message vis a vis this, I like the way the django community organized their releases. note that contrary to our "3.2 is a fixed snapshot" idea, they continue to merge bug fixes into that branch for a given period (but no feature or api changes). Each feature on the list (both "must-have" and "maybe") will have a "lieutenant" (to steal of term from the Linux community) and a committer assigned. It's OK if this is the same person, but the idea is that one committer can keep an eye and commit from patches from a number of trusted lieutenants. In most cases, the features on the todo list have obvious lieutenants; we'll need to assign missing ones and also committers. See VersionOneFeatures for the current list of lieutenants and committers. James, as the release manager, will be in charge of keeping the schedule. He'll keep track of who's working on what issues so that bug reports can be efficiently routed; he'll also nag, cajole and (if necessary) berate developers who are in danger of missing deadlines. Once 1.0 is out we'll appoint a "version manager". This person will be responsible for maintaining the 1.0 release series, which means backporting security fixes and "important" bugs and releasing 1.0.1, etc. Similarly, we'll appoint a 0.96 version manger who will do the same with 0.96. We'll continue to support 0.96 until 1.1 ships. With the 1.0 release, however, we will stop support 0.95 and earlier. This is somewhat flexible; if someone has a stake in one of those older versions we'll happily let them continue to maintain those releases, but if nobody steps up the core team won't be able to do it. http://code.djangoproject.com/wiki/VersionOneRoadmap On Mon, Jun 30, 2008 at 5:46 PM, nescivi <nescivi@...> wrote: Hiho, as this came up... I think it could be a good idea to aim for a 3.2.something release for the end of August... that way anyone who teaches SC in the upcoming academic year, can point students to that release... There have been a number of improvements since 3.2 which make it worthwhile... (from my side: some late fixes for Linux (inclusion of scvim!), some GeneralHID stuff, etc...) If we aim a release for end of August, we have some time till then to finalise and test anything we still want to fix... What do you think? sincerely, Marije _______________________________________________ sc-dev mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/ search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
	Re: 3.2.something release by Josh Parmenter :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I brought up a similar idea after 3.2 came out... that perhaps as devs we should elect / choose / beg one person to oversee the next point release. I still think it would be a good idea, and that could certainly work into what felix shows below. Josh On Jun 30, 2008, at 11:52 AM, felix wrote: vis a vis this, I like the way the django community organized their releases. note that contrary to our "3.2 is a fixed snapshot" idea, they continue to merge bug fixes into that branch for a given period (but no feature or api changes). Each feature on the list (both "must-have" and "maybe") will have a "lieutenant" (to steal of term from the Linux community) and a committer assigned. It's OK if this is the same person, but the idea is that one committer can keep an eye and commit from patches from a number of trusted lieutenants. In most cases, the features on the todo list have obvious lieutenants; we'll need to assign missing ones and also committers. See VersionOneFeatures for the current list of lieutenants and committers. James, as the release manager, will be in charge of keeping the schedule. He'll keep track of who's working on what issues so that bug reports can be efficiently routed; he'll also nag, cajole and (if necessary) berate developers who are in danger of missing deadlines. Once 1.0 is out we'll appoint a "version manager". This person will be responsible for maintaining the 1.0 release series, which means backporting security fixes and "important" bugs and releasing 1.0.1, etc. Similarly, we'll appoint a 0.96 version manger who will do the same with 0.96. We'll continue to support 0.96 until 1.1 ships. With the 1.0 release, however, we will stop support 0.95 and earlier. This is somewhat flexible; if someone has a stake in one of those older versions we'll happily let them continue to maintain those releases, but if nobody steps up the core team won't be able to do it. http://code.djangoproject.com/wiki/VersionOneRoadmap On Mon, Jun 30, 2008 at 5:46 PM, nescivi <nescivi@...> wrote: Hiho, as this came up... I think it could be a good idea to aim for a 3.2.something release for the end of August... that way anyone who teaches SC in the upcoming academic year, can point students to that release... There have been a number of improvements since 3.2 which make it worthwhile... (from my side: some late fixes for Linux (inclusion of scvim!), some GeneralHID stuff, etc...) If we aim a release for end of August, we have some time till then to finalise and test anything we still want to fix... What do you think? sincerely, Marije _______________________________________________ sc-dev mailing list info (subscribe and unsubscribe): http://swiki.hfbk-hamburg.de:8888/MusicTechnology/880 archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/ search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/ ****************************************** /* Joshua D. Parmenter http://www.realizedsound.net/josh/ “Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono */