Re: [Jack-Devel] Selecting Firewire Interface with -d

Prev	Next Index
Date	Wed, 25 Jan 2017 16:29:46 +0100
From	Thomas Brand <[hidden] at trellis dot ch>
To	Adrian Knoth <[hidden] at drcomp dot erfurt dot thur dot de>
Cc	Thomas Brand <[hidden] at trellis dot ch>, [hidden] at lists dot jackaudio dot org, [hidden] at grame dot fr
In-Reply-To	Adrian Knoth Re: [Jack-Devel] Selecting Firewire Interface with -d
Follow-Up	Stéphane Letz Re: [Jack-Devel] Selecting Firewire Interface with -d

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

Prev	Next Index

1485358269.20928_0.ltw:2,a <f60d25e0eb0adf63511b0bf1e8c83a36.squirrel at ips73 dot ips dot ch>