Menu
▾
▴
linuxsampler-devel
|
From: Rui N. C. <rn...@rn...> - 2004-06-15 23:02:39
|
Hi, As promised, Qsampler 0.0.2 has been packaged and released, along with liblscp-0.1.9.99. This release serves as a syncpoint to latest CVS on linuxsampler.org. Please find the respective tarballs and selected RPMs on the following sites: http://sourceforge.net/projects/qsampler http://qsampler.sourceforge.net http://www.rncbc.org/ls Soon this will be officially featured on the linuxsampler.org downloads section. Enjoy. -- rncbc aka Rui Nuno Capela rn...@rn... |
|
From: Mark K. <mk...@co...> - 2004-06-21 13:44:23
|
Rui Nuno Capela wrote: > Hi, > > As promised, Qsampler 0.0.2 has been packaged and released, along with > liblscp-0.1.9.99. > > This release serves as a syncpoint to latest CVS on linuxsampler.org. > Please find the respective tarballs and selected RPMs on the following > sites: > > http://sourceforge.net/projects/qsampler > http://qsampler.sourceforge.net > http://www.rncbc.org/ls > > Soon this will be officially featured on the linuxsampler.org downloads > section. > > Enjoy. Hi all, Been away for a week. Is there anything specific for me to look at? Looks like there is headway on the programming side. Lots of lex/bison stuff? Anyway, I'm back so let me know if there are specific things you want me to look at. Should I download from CVS or Rui's web site? (Rui's seems to be a bit easier if it's up to date.) BTW - what were the issues just before I left about 'tuning'? I wonder if we should set up a real bug reporting system where we could log issues about specific gig files instead of trying to track them in email? I'm open to any method that works. Cheers, Mark |
|
From: Rui N. C. <rn...@rn...> - 2004-06-21 14:47:59
|
Hi Mark, > > Hi all, > Been away for a week. Is there anything specific for me to look at? > Looks like there is headway on the programming side. Lots of lex/bison > stuff? > > Anyway, I'm back so let me know if there are specific things you > want me to look at. > > Should I download from CVS or Rui's web site? (Rui's seems to be a > bit easier if it's up to date.) > Current linuxsampler CVS HEAD is pretty unstable, and somewhat broke regarding compability with client/server interface as it was before June 13th's revolution :) The packages on my site and qsampler.sf.net are related to the pre-revolutionary period, only. > > BTW - what were the issues just before I left about 'tuning'? I > wonder if we should set up a real bug reporting system where we could > log issues about specific gig files instead of trying to track them in > email? > How about setting up a bugtracker on ls.org ? Something like Mantis Bugtracker (http://www.mantisbt.org), exactly the same tool the ardour and alsa teams are using. PHP/MySQL required. Cheers. -- rncbc aka Rui Nuno Capela rn...@rn... |
|
From: Mark K. <mk...@co...> - 2004-06-21 16:08:24
|
Rui Nuno Capela wrote: > Hi Mark, > Current linuxsampler CVS HEAD is pretty unstable, and somewhat broke > regarding compability with client/server interface as it was before June > 13th's revolution :) > > The packages on my site and qsampler.sf.net are related to the > pre-revolutionary period, only. OK, I won't bother until you folks get to a point where you think it's worth my time. Let me know when. > How about setting up a bugtracker on ls.org ? Something like Mantis > Bugtracker (http://www.mantisbt.org), exactly the same tool the ardour and > alsa teams are using. PHP/MySQL required. > > Cheers. I like this idea a lot. I think there could be different basic areas that we log both bugs and feature requests: 1) LS 2) QS 3) Sound card/Alsa 4) MIDI 5) Gig file compatibility I'm sure there are others. I think having a bug tracker is great since the data doesn't get lost or forgotten. Rosegarden also uses a bug tracker, but it looks different than the Alsa bug tracker, so maybe that's another option. Personally I like the Alsa one a bit more as it's more searchable, but maybe that's just the way they've set it up. I think it's part of Sourceforge, or seems to be. Also, Gentoo uses a bug tracker that's quite involved. Don't know if that's an option to look at. Cheers, Mark |
|
From: <be...@ga...> - 2004-06-21 20:27:29
|
Scrive Rui Nuno Capela <rn...@rn...>: > > > > How about setting up a bugtracker on ls.org ? Something like Mantis > Bugtracker (http://www.mantisbt.org), exactly the same tool the ardour and > alsa teams are using. PHP/MySQL required. > Hi, yes Mantis seems very nice. (the idea of bug tracking categories mentioned by mark makes sense, even for "bugs" related to GIG files that experience glitches (which means that the LS gig engine has a bug) PHP is active on ls.org , for mysql just mail me and I'll create a mysql db that we can use for mantis. cheers, Benno http://www.linuxsampler.org ------------------------------------------------- This mail sent through http://www.gardena.net |
|
From: Christian S. <sch...@so...> - 2004-06-22 08:15:59
|
Es geschah am Montag, 21. Juni 2004 16:08 als Rui Nuno Capela schrieb: > How about setting up a bugtracker on ls.org ? Something like Mantis > Bugtracker (http://www.mantisbt.org), exactly the same tool the ardour and > alsa teams are using. PHP/MySQL required. We planned to use a bug tracking system when we go for the first release, means when all major features for the first release are *done* and we reached the stage to just fix things for the release. At the moment there's still too much to do anyway. I can install a bug tracking system when my exams are over. CU Christian |
Thanks for helping keep SourceForge clean.
X