I have updated the notes for the changes in the last month. Incomplete
naturally.  git-log records in need of noting or deleting below.  Any
assistance welcome

==John ffitch

commit 1191a12cf38048437286295297b55f9997e101e0 (HEAD -> develop, origin/develop)
Author: veplaini 
Date:   Sat Oct 14 12:30:28 2017 +0100

    server commands

commit 6a708242f7f5061145bdb35b184f9d00a76d7f35
Author: veplaini 
Date:   Sat Oct 14 10:14:17 2017 +0100

    faust opcodes build


commit 418fd15f591d5333958c0bddf6417d02cd5a1316
Author: Steven Yi 
Date:   Fri Oct 13 16:15:06 2017 -0400

    applied Albert Graef's change for ignoring of -ENOENT error code

commit 321f81f7a8a763bf32b16690caae921785292474
Author: veplaini 
Date:   Fri Oct 13 16:14:03 2017 +0100

    return value from async functions

commit 135361d543605efff197afd26531b932c2e90a58
Author: veplaini 
Date:   Fri Oct 13 13:39:58 2017 +0100

    lock free code completed, not fully tested, Async API functions also supplied

commit 7a417d79b7aa4b1a8181f7eb524c36956456e6e7
Author: veplaini 
Date:   Fri Oct 13 09:37:29 2017 +0100

    asynchronous mechanism for compile and kill instance in place

commit cb96b4e8f179be941398856d10587ae16e381249
Author: veplaini 
Date:   Thu Oct 12 14:12:40 2017 +0100

    async API functions

Author: veplaini 
Date:   Thu Oct 12 11:43:42 2017 +0100

    memory model for atomic in queue

commit 9eaeecf51c3ef9d80e340cb1576d48f50e9089e4
Author: veplaini 
Date:   Tue Oct 3 11:44:44 2017 +0100

    chnget/set with k strings

commit e39f570503b5628bf77034de9a3590fbf87bcd5c
Author: gogins 
Date:   Sat Sep 23 21:29:08 2017 -0400

    Trying to get VST features building on AppVeyor (#793).

commit da9dfebca45abfc80b41260725bd4ff17becfcce
Author: Michael Gogins 
Date:   Sat Sep 23 11:09:29 2017 -0400

    Updated with license exception in VST related code.

would it be possible to include eduardo moguillansky's contributions 
(sc_...)?  i think there were some problems in the work flow, but many 
were interested to see these new opcodes in csound (and have a 
contribution from a new developer).

	joachim


On 14/10/17 22:59, jpff wrote:
> I have updated the notes for the changes in the last month. Incomplete
> naturally.  git-log records in need of noting or deleting below.  Any
> assistance welcome
>
> ==John ffitch
>
> commit 1191a12cf38048437286295297b55f9997e101e0 (HEAD -> develop, origin/develop)
> Author: veplaini 
> Date:   Sat Oct 14 12:30:28 2017 +0100
>
>     server commands
>
> commit 6a708242f7f5061145bdb35b184f9d00a76d7f35
> Author: veplaini 
> Date:   Sat Oct 14 10:14:17 2017 +0100
>
>     faust opcodes build
>
>
> commit 418fd15f591d5333958c0bddf6417d02cd5a1316
> Author: Steven Yi 
> Date:   Fri Oct 13 16:15:06 2017 -0400
>
>     applied Albert Graef's change for ignoring of -ENOENT error code
>
> commit 321f81f7a8a763bf32b16690caae921785292474
> Author: veplaini 
> Date:   Fri Oct 13 16:14:03 2017 +0100
>
>     return value from async functions
>
> commit 135361d543605efff197afd26531b932c2e90a58
> Author: veplaini 
> Date:   Fri Oct 13 13:39:58 2017 +0100
>
>     lock free code completed, not fully tested, Async API functions also supplied
>
> commit 7a417d79b7aa4b1a8181f7eb524c36956456e6e7
> Author: veplaini 
> Date:   Fri Oct 13 09:37:29 2017 +0100
>
>     asynchronous mechanism for compile and kill instance in place
>
> commit cb96b4e8f179be941398856d10587ae16e381249
> Author: veplaini 
> Date:   Thu Oct 12 14:12:40 2017 +0100
>
>     async API functions
>
> Author: veplaini 
> Date:   Thu Oct 12 11:43:42 2017 +0100
>
>     memory model for atomic in queue
>
> commit 9eaeecf51c3ef9d80e340cb1576d48f50e9089e4
> Author: veplaini 
> Date:   Tue Oct 3 11:44:44 2017 +0100
>
>     chnget/set with k strings
>
> commit e39f570503b5628bf77034de9a3590fbf87bcd5c
> Author: gogins 
> Date:   Sat Sep 23 21:29:08 2017 -0400
>
>     Trying to get VST features building on AppVeyor (#793).
>
> commit da9dfebca45abfc80b41260725bd4ff17becfcce
> Author: Michael Gogins 
> Date:   Sat Sep 23 11:09:29 2017 -0400
>
>     Updated with license exception in VST related code.
>
> =========ed======

The sc_ opcodes were in 6.09 and in release Notes.  I am not aware of any 
others


On Mon, 16 Oct 2017, joachim heintz wrote:

> would it be possible to include eduardo moguillansky's contributions 
> (sc_...)?  i think there were some problems in the work flow, but many were 
> interested to see these new opcodes in csound (and have a contribution from a 
> new developer).
>
> 	joachim
>
>
> On 14/10/17 22:59, jpff wrote:
>> I have updated the notes for the changes in the last month. Incomplete
>> naturally.  git-log records in need of noting or deleting below.  Any
>> assistance welcome
>> 
>> ==John ffitch

Eduardo had tried to use Pull Requests but both times didn't work out
(the first modified every single file in the code base; the second one
needed multiple changes). Both PRs were reviewed and changes were
requested. These are in 846 and 847:

https://github.com/csound/csound/pull/846
https://github.com/csound/csound/pull/847

There were a number of rounds of changes requested and required and,
IMO, with all good reason.  (No, we can't take code when there are
licensing issues.  No, we can't apply a PR when there are extraneous
files. No, we don't as a rule take opcodes without documentation.)
Eduardo was great to reply and work through the changes but the
process dragged on a while. When asked for additional fixes to the PR
in 847 and for documentation on the new opcodes the PR was withdrawn.

I asked off-list if he wanted to have his work integrated directly by
one of us since the PR revisions didn't get to a point where they
could be merged, but I have not heard anything.

At this point, I don't think there's much more to do on our side.  We
went through the PR process and did it the right way to pre-review
changes before integrating contributions into the code base. We did
indeed catch issues.  Everyone spent a lot of their personal time to
move it forward.  I think we'd all be happy for the contributions to
make their way into Csound but right now, since they've been
withdrawn, there's nothing to do as far as I can see.



On Mon, Oct 16, 2017 at 11:25 AM, jpff  wrote:
> The sc_ opcodes were in 6.09 and in release Notes.  I am not aware of any
> others
>
>
>
> On Mon, 16 Oct 2017, joachim heintz wrote:
>
>> would it be possible to include eduardo moguillansky's contributions
>> (sc_...)?  i think there were some problems in the work flow, but many were
>> interested to see these new opcodes in csound (and have a contribution from
>> a new developer).
>>
>>         joachim
>>
>>
>> On 14/10/17 22:59, jpff wrote:
>>>
>>> I have updated the notes for the changes in the last month. Incomplete
>>> naturally.  git-log records in need of noting or deleting below.  Any
>>> assistance welcome
>>>
>>> ==John ffitch
>>>

ok — i did not know this end of the story in detail.  thanks for the 
explanations.  so it is as it is.


On 16/10/17 18:22, Steven Yi wrote:
> Eduardo had tried to use Pull Requests but both times didn't work out
> (the first modified every single file in the code base; the second one
> needed multiple changes). Both PRs were reviewed and changes were
> requested. These are in 846 and 847:
>
> https://github.com/csound/csound/pull/846
> https://github.com/csound/csound/pull/847
>
> There were a number of rounds of changes requested and required and,
> IMO, with all good reason.  (No, we can't take code when there are
> licensing issues.  No, we can't apply a PR when there are extraneous
> files. No, we don't as a rule take opcodes without documentation.)
> Eduardo was great to reply and work through the changes but the
> process dragged on a while. When asked for additional fixes to the PR
> in 847 and for documentation on the new opcodes the PR was withdrawn.
>
> I asked off-list if he wanted to have his work integrated directly by
> one of us since the PR revisions didn't get to a point where they
> could be merged, but I have not heard anything.
>
> At this point, I don't think there's much more to do on our side.  We
> went through the PR process and did it the right way to pre-review
> changes before integrating contributions into the code base. We did
> indeed catch issues.  Everyone spent a lot of their personal time to
> move it forward.  I think we'd all be happy for the contributions to
> make their way into Csound but right now, since they've been
> withdrawn, there's nothing to do as far as I can see.
>
>
>
> On Mon, Oct 16, 2017 at 11:25 AM, jpff  wrote:
>> The sc_ opcodes were in 6.09 and in release Notes.  I am not aware of any
>> others
>>
>>
>>
>> On Mon, 16 Oct 2017, joachim heintz wrote:
>>
>>> would it be possible to include eduardo moguillansky's contributions
>>> (sc_...)?  i think there were some problems in the work flow, but many were
>>> interested to see these new opcodes in csound (and have a contribution from
>>> a new developer).
>>>
>>>         joachim
>>>
>>>
>>> On 14/10/17 22:59, jpff wrote:
>>>>
>>>> I have updated the notes for the changes in the last month. Incomplete
>>>> naturally.  git-log records in need of noting or deleting below.  Any
>>>> assistance welcome
>>>>
>>>> ==John ffitch
>>>>
>>