[Jack-Devel] Selecting Firewire Interface with -d

Stéphane Letz letz at grame.fr
Wed Jan 25 16:37:26 CET 2017

Not much time for JACK2 right now. Merging big PR is almost impossible if they affect common code and cannot be tested on OS X and Windows. PR that deal with limited/easy to review changes or Linux/ALSA specific ones can possibly be merged. PR review is a good idea, but I would prefer to keep an eye on final merge... 

The reasonable goal for me will be to finally do a official jackdmp 1.9.1 release, hopefully in february.


> Le 25 janv. 2017 à 16:29, Thomas Brand <tom at trellis.ch> a écrit :
> On Tue, January 24, 2017 22:02, Adrian Knoth wrote:
>> And then there's this whole category of OSX. I don't know what the
>> situation there is, but it seems that Sierra changed the device API and
>> jack no longer works? Or maybe I'm reading this wrong?
>> Let me CC sletz for his view. I haven't seen him lately neither, maybe
>> also swamped with work.
>> That said, if you want to provide code reviews on the PRs, please go
>> ahead and mark those that look good to you. Then re-assign to me, and I'll
>> merge them in. The more eyes the merrier.
> I don't think i could do that in a nice way for pull requests since i've
> only a very rough insight in JACK 2's code base.
> However i could possibly help to categorize issues by labels.
> Please have a look at this example:
> https://github.com/andrewrk/libsoundio/issues
> I think it makes great use of labels to get a quick overview if an issue
> is a bug or a feature or related to OSX etc. The first step would be to
> define a set of labels.
> What is the general opinion, would that help in any ways? Could it help to
> plan releases too (using milestones)?
> Greetings
> Thomas

More information about the Jackaudio mailing list