Hi All,

Should we go ahead with the 6.06 release?  It looks to me that the
6.06 folder on SF is live.  We have the same files--minus source
releases, which we can just use the auto-generated ones--staged on
Github.

Sure -- it needs to be out before the bugs overtake it.  Do we still need 
a manual?


On Mon, 12 Oct 2015, Steven Yi wrote:

> Hi All,
>
> Should we go ahead with the 6.06 release?  It looks to me that the
> 6.06 folder on SF is live.  We have the same files--minus source
> releases, which we can just use the auto-generated ones--staged on
> Github.
>
> steven

I think we need a manual release.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 12 Oct 2015, at 20:08, jpff  wrote:
> 
> Sure -- it needs to be out before the bugs overtake it.  Do we still need a manual?
> 
> 
>> On Mon, 12 Oct 2015, Steven Yi wrote:
>> 
>> Hi All,
>> 
>> Should we go ahead with the 6.06 release?  It looks to me that the
>> 6.06 folder on SF is live.  We have the same files--minus source
>> releases, which we can just use the auto-generated ones--staged on
>> Github.
>> 
>> steven

I think the sources are OK now icluding a "what's new" section.  Basic 
manual should be "easy", but the variants might take a little longer.
==John ff
<


On Mon, 12 Oct 2015, Victor Lazzarini wrote:

> I think we need a manual release.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 12 Oct 2015, at 20:08, jpff  wrote:
>>
>> Sure -- it needs to be out before the bugs overtake it.  Do we still need a manual?
>>
>>
>>> On Mon, 12 Oct 2015, Steven Yi wrote:
>>>
>>> Hi All,
>>>
>>> Should we go ahead with the 6.06 release?  It looks to me that the
>>> 6.06 folder on SF is live.  We have the same files--minus source
>>> releases, which we can just use the auto-generated ones--staged on
>>> Github.
>>>
>>> steven
>>>

yes, these opcodes never existed
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 13 Oct 2015, at 08:33, Francois PINOT  wrote:
> 
> I noticed that John removed references to chnrecv/chnsend from the manual on september 3rd. Is this a definitive action?
> 
> Francois
> 
> 2015-10-13 1:22 GMT+02:00 Francois PINOT :
> I'll build the different manual packages tomorrow and I'll send a link to John for downloading.
> 
> Francois
> 
> 2015-10-12 21:46 GMT+02:00 jpff :
> I think the sources are OK now icluding a "what's new" section.  Basic manual should be "easy", but the variants might take a little longer.
> ==John ff
> <
> 
> 
> On Mon, 12 Oct 2015, Victor Lazzarini wrote:
> 
> I think we need a manual release.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
> On 12 Oct 2015, at 20:08, jpff  wrote:
> 
> Sure -- it needs to be out before the bugs overtake it.  Do we still need a manual?
> 
> 
> On Mon, 12 Oct 2015, Steven Yi wrote:
> 
> Hi All,
> 
> Should we go ahead with the 6.06 release?  It looks to me that the
> 6.06 folder on SF is live.  We have the same files--minus source
> releases, which we can just use the auto-generated ones--staged on
> Github.
> 
> steven
> 
> 
> 

Hi All,

It's been some time and I'd like to close out the release branch.
Shall we go ahead with that and announce the release?

steven

On Tue, Oct 13, 2015 at 7:49 AM, Francois PINOT  wrote:
> I just built the 10 packages of the manual for the new release of Csound.
> You can get them here http://fggp.org/csound/manual-packages/ and upload
> them on SF.
>
> Francois
>
> 2015-10-13 10:03 GMT+02:00 Victor Lazzarini :
>>
>> yes, these opcodes never existed
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 13 Oct 2015, at 08:33, Francois PINOT  wrote:
>> >
>> > I noticed that John removed references to chnrecv/chnsend from the
>> > manual on september 3rd. Is this a definitive action?
>> >
>> > Francois
>> >
>> > 2015-10-13 1:22 GMT+02:00 Francois PINOT :
>> > I'll build the different manual packages tomorrow and I'll send a link
>> > to John for downloading.
>> >
>> > Francois
>> >
>> > 2015-10-12 21:46 GMT+02:00 jpff :
>> > I think the sources are OK now icluding a "what's new" section.  Basic
>> > manual should be "easy", but the variants might take a little longer.
>> > ==John ff
>> > <
>> >
>> >
>> > On Mon, 12 Oct 2015, Victor Lazzarini wrote:
>> >
>> > I think we need a manual release.
>> >
>> > Victor Lazzarini
>> > Dean of Arts, Celtic Studies, and Philosophy
>> > Maynooth University
>> > Ireland
>> >
>> > On 12 Oct 2015, at 20:08, jpff  wrote:
>> >
>> > Sure -- it needs to be out before the bugs overtake it.  Do we still
>> > need a manual?
>> >
>> >
>> > On Mon, 12 Oct 2015, Steven Yi wrote:
>> >
>> > Hi All,
>> >
>> > Should we go ahead with the 6.06 release?  It looks to me that the
>> > 6.06 folder on SF is live.  We have the same files--minus source
>> > releases, which we can just use the auto-generated ones--staged on
>> > Github.
>> >
>> > steven
>> >
>> >
>> >
>> >
>

I am not done with the WIndows release, and I am sure I will have to
make changes to the code and build files in the release branch.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Wed, Oct 21, 2015 at 3:52 PM, Steven Yi  wrote:
> Hi All,
>
> It's been some time and I'd like to close out the release branch.
> Shall we go ahead with that and announce the release?
>
> steven
>
> On Tue, Oct 13, 2015 at 7:49 AM, Francois PINOT  wrote:
>> I just built the 10 packages of the manual for the new release of Csound.
>> You can get them here http://fggp.org/csound/manual-packages/ and upload
>> them on SF.
>>
>> Francois
>>
>> 2015-10-13 10:03 GMT+02:00 Victor Lazzarini :
>>>
>>> yes, these opcodes never existed
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>> > On 13 Oct 2015, at 08:33, Francois PINOT  wrote:
>>> >
>>> > I noticed that John removed references to chnrecv/chnsend from the
>>> > manual on september 3rd. Is this a definitive action?
>>> >
>>> > Francois
>>> >
>>> > 2015-10-13 1:22 GMT+02:00 Francois PINOT :
>>> > I'll build the different manual packages tomorrow and I'll send a link
>>> > to John for downloading.
>>> >
>>> > Francois
>>> >
>>> > 2015-10-12 21:46 GMT+02:00 jpff :
>>> > I think the sources are OK now icluding a "what's new" section.  Basic
>>> > manual should be "easy", but the variants might take a little longer.
>>> > ==John ff
>>> > <
>>> >
>>> >
>>> > On Mon, 12 Oct 2015, Victor Lazzarini wrote:
>>> >
>>> > I think we need a manual release.
>>> >
>>> > Victor Lazzarini
>>> > Dean of Arts, Celtic Studies, and Philosophy
>>> > Maynooth University
>>> > Ireland
>>> >
>>> > On 12 Oct 2015, at 20:08, jpff  wrote:
>>> >
>>> > Sure -- it needs to be out before the bugs overtake it.  Do we still
>>> > need a manual?
>>> >
>>> >
>>> > On Mon, 12 Oct 2015, Steven Yi wrote:
>>> >
>>> > Hi All,
>>> >
>>> > Should we go ahead with the 6.06 release?  It looks to me that the
>>> > 6.06 folder on SF is live.  We have the same files--minus source
>>> > releases, which we can just use the auto-generated ones--staged on
>>> > Github.
>>> >
>>> > steven
>>> >
>>> >
>>> >
>>> >
>>

I'm on a business trip for a week and will only be able to start
working on the Windows release starting next Monday. If this is a
problem, go ahead and merge back the release branch and I will create
another release branch just for Windows.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Wed, Oct 21, 2015 at 4:13 PM, Michael Gogins
 wrote:
> I am not done with the WIndows release, and I am sure I will have to
> make changes to the code and build files in the release branch.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Wed, Oct 21, 2015 at 3:52 PM, Steven Yi  wrote:
>> Hi All,
>>
>> It's been some time and I'd like to close out the release branch.
>> Shall we go ahead with that and announce the release?
>>
>> steven
>>
>> On Tue, Oct 13, 2015 at 7:49 AM, Francois PINOT  wrote:
>>> I just built the 10 packages of the manual for the new release of Csound.
>>> You can get them here http://fggp.org/csound/manual-packages/ and upload
>>> them on SF.
>>>
>>> Francois
>>>
>>> 2015-10-13 10:03 GMT+02:00 Victor Lazzarini :
>>>>
>>>> yes, these opcodes never existed
>>>> ========================
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>> > On 13 Oct 2015, at 08:33, Francois PINOT  wrote:
>>>> >
>>>> > I noticed that John removed references to chnrecv/chnsend from the
>>>> > manual on september 3rd. Is this a definitive action?
>>>> >
>>>> > Francois
>>>> >
>>>> > 2015-10-13 1:22 GMT+02:00 Francois PINOT :
>>>> > I'll build the different manual packages tomorrow and I'll send a link
>>>> > to John for downloading.
>>>> >
>>>> > Francois
>>>> >
>>>> > 2015-10-12 21:46 GMT+02:00 jpff :
>>>> > I think the sources are OK now icluding a "what's new" section.  Basic
>>>> > manual should be "easy", but the variants might take a little longer.
>>>> > ==John ff
>>>> > <
>>>> >
>>>> >
>>>> > On Mon, 12 Oct 2015, Victor Lazzarini wrote:
>>>> >
>>>> > I think we need a manual release.
>>>> >
>>>> > Victor Lazzarini
>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>> > Maynooth University
>>>> > Ireland
>>>> >
>>>> > On 12 Oct 2015, at 20:08, jpff  wrote:
>>>> >
>>>> > Sure -- it needs to be out before the bugs overtake it.  Do we still
>>>> > need a manual?
>>>> >
>>>> >
>>>> > On Mon, 12 Oct 2015, Steven Yi wrote:
>>>> >
>>>> > Hi All,
>>>> >
>>>> > Should we go ahead with the 6.06 release?  It looks to me that the
>>>> > 6.06 folder on SF is live.  We have the same files--minus source
>>>> > releases, which we can just use the auto-generated ones--staged on
>>>> > Github.
>>>> >
>>>> > steven
>>>> >
>>>> >
>>>> >
>>>> >
>>>

Hi All,

What's going on with the release now?  It's getting close to a month
since the release builds were done.  I'm seeing changes that look
release related in the develop branch for Windows, which makes me
think the Windows build is going to not be the same as what we already
built.  Should I got ahead and close out the release branch?

steven

On Wed, Oct 28, 2015 at 9:38 AM, Michael Gogins
 wrote:
> I'm on a business trip for a week and will only be able to start
> working on the Windows release starting next Monday. If this is a
> problem, go ahead and merge back the release branch and I will create
> another release branch just for Windows.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Wed, Oct 21, 2015 at 4:13 PM, Michael Gogins
>  wrote:
>> I am not done with the WIndows release, and I am sure I will have to
>> make changes to the code and build files in the release branch.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Wed, Oct 21, 2015 at 3:52 PM, Steven Yi  wrote:
>>> Hi All,
>>>
>>> It's been some time and I'd like to close out the release branch.
>>> Shall we go ahead with that and announce the release?
>>>
>>> steven
>>>
>>> On Tue, Oct 13, 2015 at 7:49 AM, Francois PINOT  wrote:
>>>> I just built the 10 packages of the manual for the new release of Csound.
>>>> You can get them here http://fggp.org/csound/manual-packages/ and upload
>>>> them on SF.
>>>>
>>>> Francois
>>>>
>>>> 2015-10-13 10:03 GMT+02:00 Victor Lazzarini :
>>>>>
>>>>> yes, these opcodes never existed
>>>>> ========================
>>>>> Dr Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>> > On 13 Oct 2015, at 08:33, Francois PINOT  wrote:
>>>>> >
>>>>> > I noticed that John removed references to chnrecv/chnsend from the
>>>>> > manual on september 3rd. Is this a definitive action?
>>>>> >
>>>>> > Francois
>>>>> >
>>>>> > 2015-10-13 1:22 GMT+02:00 Francois PINOT :
>>>>> > I'll build the different manual packages tomorrow and I'll send a link
>>>>> > to John for downloading.
>>>>> >
>>>>> > Francois
>>>>> >
>>>>> > 2015-10-12 21:46 GMT+02:00 jpff :
>>>>> > I think the sources are OK now icluding a "what's new" section.  Basic
>>>>> > manual should be "easy", but the variants might take a little longer.
>>>>> > ==John ff
>>>>> > <
>>>>> >
>>>>> >
>>>>> > On Mon, 12 Oct 2015, Victor Lazzarini wrote:
>>>>> >
>>>>> > I think we need a manual release.
>>>>> >
>>>>> > Victor Lazzarini
>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>> > Maynooth University
>>>>> > Ireland
>>>>> >
>>>>> > On 12 Oct 2015, at 20:08, jpff  wrote:
>>>>> >
>>>>> > Sure -- it needs to be out before the bugs overtake it.  Do we still
>>>>> > need a manual?
>>>>> >
>>>>> >
>>>>> > On Mon, 12 Oct 2015, Steven Yi wrote:
>>>>> >
>>>>> > Hi All,
>>>>> >
>>>>> > Should we go ahead with the 6.06 release?  It looks to me that the
>>>>> > 6.06 folder on SF is live.  We have the same files--minus source
>>>>> > releases, which we can just use the auto-generated ones--staged on
>>>>> > Github.
>>>>> >
>>>>> > steven
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>

That is what I said before, close out the release branch. I will have
do a different branch for the Windows release. In fact I think this
should probably be the policy going forward, because the Windows
issues are so different from the other issues.

I am continuing to have problems building the CsoundApplication for
both Android 4.4 and Android 5. I am running into issues that have
been reported on Stack Exchange etc. (missing "srand" function e.g.),
but the solutions and workarounds that I find are not working for us.


-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, Nov 9, 2015 at 10:24 AM, Steven Yi  wrote:
> Hi All,
>
> What's going on with the release now?  It's getting close to a month
> since the release builds were done.  I'm seeing changes that look
> release related in the develop branch for Windows, which makes me
> think the Windows build is going to not be the same as what we already
> built.  Should I got ahead and close out the release branch?
>
> steven
>
> On Wed, Oct 28, 2015 at 9:38 AM, Michael Gogins
>  wrote:
>> I'm on a business trip for a week and will only be able to start
>> working on the Windows release starting next Monday. If this is a
>> problem, go ahead and merge back the release branch and I will create
>> another release branch just for Windows.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Wed, Oct 21, 2015 at 4:13 PM, Michael Gogins
>>  wrote:
>>> I am not done with the WIndows release, and I am sure I will have to
>>> make changes to the code and build files in the release branch.
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Wed, Oct 21, 2015 at 3:52 PM, Steven Yi  wrote:
>>>> Hi All,
>>>>
>>>> It's been some time and I'd like to close out the release branch.
>>>> Shall we go ahead with that and announce the release?
>>>>
>>>> steven
>>>>
>>>> On Tue, Oct 13, 2015 at 7:49 AM, Francois PINOT  wrote:
>>>>> I just built the 10 packages of the manual for the new release of Csound.
>>>>> You can get them here http://fggp.org/csound/manual-packages/ and upload
>>>>> them on SF.
>>>>>
>>>>> Francois
>>>>>
>>>>> 2015-10-13 10:03 GMT+02:00 Victor Lazzarini :
>>>>>>
>>>>>> yes, these opcodes never existed
>>>>>> ========================
>>>>>> Dr Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>> > On 13 Oct 2015, at 08:33, Francois PINOT  wrote:
>>>>>> >
>>>>>> > I noticed that John removed references to chnrecv/chnsend from the
>>>>>> > manual on september 3rd. Is this a definitive action?
>>>>>> >
>>>>>> > Francois
>>>>>> >
>>>>>> > 2015-10-13 1:22 GMT+02:00 Francois PINOT :
>>>>>> > I'll build the different manual packages tomorrow and I'll send a link
>>>>>> > to John for downloading.
>>>>>> >
>>>>>> > Francois
>>>>>> >
>>>>>> > 2015-10-12 21:46 GMT+02:00 jpff :
>>>>>> > I think the sources are OK now icluding a "what's new" section.  Basic
>>>>>> > manual should be "easy", but the variants might take a little longer.
>>>>>> > ==John ff
>>>>>> > <
>>>>>> >
>>>>>> >
>>>>>> > On Mon, 12 Oct 2015, Victor Lazzarini wrote:
>>>>>> >
>>>>>> > I think we need a manual release.
>>>>>> >
>>>>>> > Victor Lazzarini
>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>> > Maynooth University
>>>>>> > Ireland
>>>>>> >
>>>>>> > On 12 Oct 2015, at 20:08, jpff  wrote:
>>>>>> >
>>>>>> > Sure -- it needs to be out before the bugs overtake it.  Do we still
>>>>>> > need a manual?
>>>>>> >
>>>>>> >
>>>>>> > On Mon, 12 Oct 2015, Steven Yi wrote:
>>>>>> >
>>>>>> > Hi All,
>>>>>> >
>>>>>> > Should we go ahead with the 6.06 release?  It looks to me that the
>>>>>> > 6.06 folder on SF is live.  We have the same files--minus source
>>>>>> > releases, which we can just use the auto-generated ones--staged on
>>>>>> > Github.
>>>>>> >
>>>>>> > steven
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>

Seeing how many  fixes/changes there have been maybe we should release 

I've finished the 6.06.0 release branch. Changes have been merged into
master and develop.

6.07 makes sense.  For Windows, I do not think releases for that
platform should be out of sync and use commits outside of the ones
used for other platforms.  It makes it difficult to track bugs
introduced/fixed per version released.

For moving forward, I think we should move the Windows build to be
fully automated, same as it is for OSX, Linux, Android, iOS, Web, etc.
The lag time and mismatching of versions is not good, IMO.

steven

On Mon, Nov 9, 2015 at 10:41 AM, jpff  wrote:

So we will not have a 6.06 for Windows?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 9 Nov 2015, at 19:56, Steven Yi  wrote:
> 
> I've finished the 6.06.0 release branch. Changes have been merged into
> master and develop.
> 
> 6.07 makes sense.  For Windows, I do not think releases for that
> platform should be out of sync and use commits outside of the ones
> used for other platforms.  It makes it difficult to track bugs
> introduced/fixed per version released.
> 
> For moving forward, I think we should move the Windows build to be
> fully automated, same as it is for OSX, Linux, Android, iOS, Web, etc.
> The lag time and mismatching of versions is not good, IMO.
> 
> steven
> 
>> On Mon, Nov 9, 2015 at 10:41 AM, jpff  wrote:
>> Seeing how many  fixes/changes there have been maybe we should release 6.

The WIndows release is a big pain for everyone, especially me. I will
be ecstatic when an automatic system cross-compiles it on Linux with
all the current features. In the meantime, to accommodate the
difficulties, I suggest that I skip the Windows installer for version
6.06.0, but go right ahead and release a point version of the Windows
installer, 6.06.1, in a few days.

The only remaining issue is getting Android Studio and its version of
the NDK to build the CsoundApplication so it will run on both Android
4.4 and more recent versions. Of course this is not a Windows issue,
but I have always done the Android application release and the Windows
release as part of the general release process.

Then for 6.07.0 I should be able to easily do both releases again
since I have already done most of the hard work, 6.0.5 was quite easy.

How does that sound?

Regards,,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, Nov 9, 2015 at 3:02 PM, Victor Lazzarini
 wrote:
> So we will not have a 6.06 for Windows?
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 9 Nov 2015, at 19:56, Steven Yi  wrote:
>>
>> I've finished the 6.06.0 release branch. Changes have been merged into
>> master and develop.
>>
>> 6.07 makes sense.  For Windows, I do not think releases for that
>> platform should be out of sync and use commits outside of the ones
>> used for other platforms.  It makes it difficult to track bugs
>> introduced/fixed per version released.
>>
>> For moving forward, I think we should move the Windows build to be
>> fully automated, same as it is for OSX, Linux, Android, iOS, Web, etc.
>> The lag time and mismatching of versions is not good, IMO.
>>
>> steven
>>
>>> On Mon, Nov 9, 2015 at 10:41 AM, jpff  wrote:

I may have got to the bottom of the Android versioning problem with
Android Studio.

There appears to be a bug in Android Studio
(https://code.google.com/p/android/issues/detail?id=177530). For
specifying backward compileSdkVersion (AKA "build target") to run on
both Android 4.4 and on versions 5 and above, the project needs to
have compileSdkVersion defined as 19 or lower in the project level
build.gradle file as well as in all the NDK builds. But the Csound
Android project has a project level build file that is not an Android
module, it is a container for other modules. In that case, the bug
causes Android Studio's gradle plugin to use the highest available
compileSdkVersion, which has a runtime library that does not define
srand etc.

I can think of several workarounds but I need to get the current
releases finished and uploaded.

Therefore, I am going to defer a new build of the Csound for Android
application that will run on Android 4.4 for the time being.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, Nov 9, 2015 at 6:26 PM, Michael Gogins  wrote:
> The WIndows release is a big pain for everyone, especially me. I will
> be ecstatic when an automatic system cross-compiles it on Linux with
> all the current features. In the meantime, to accommodate the
> difficulties, I suggest that I skip the Windows installer for version
> 6.06.0, but go right ahead and release a point version of the Windows
> installer, 6.06.1, in a few days.
>
> The only remaining issue is getting Android Studio and its version of
> the NDK to build the CsoundApplication so it will run on both Android
> 4.4 and more recent versions. Of course this is not a Windows issue,
> but I have always done the Android application release and the Windows
> release as part of the general release process.
>
> Then for 6.07.0 I should be able to easily do both releases again
> since I have already done most of the hard work, 6.0.5 was quite easy.
>
> How does that sound?
>
> Regards,,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Mon, Nov 9, 2015 at 3:02 PM, Victor Lazzarini
>  wrote:
>> So we will not have a 6.06 for Windows?
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>>> On 9 Nov 2015, at 19:56, Steven Yi  wrote:
>>>
>>> I've finished the 6.06.0 release branch. Changes have been merged into
>>> master and develop.
>>>
>>> 6.07 makes sense.  For Windows, I do not think releases for that
>>> platform should be out of sync and use commits outside of the ones
>>> used for other platforms.  It makes it difficult to track bugs
>>> introduced/fixed per version released.
>>>
>>> For moving forward, I think we should move the Windows build to be
>>> fully automated, same as it is for OSX, Linux, Android, iOS, Web, etc.
>>> The lag time and mismatching of versions is not good, IMO.
>>>
>>> steven
>>>
>>>> On Mon, Nov 9, 2015 at 10:41 AM, jpff  wrote:

I'm not sure how far we can get with the cross-compilation build, but
it would be nice if it could be done on Linux.  I think we'd still
need an on-Windows automated build, perhaps with MSVC and NuGet, but I
suppose that all requires more research.

I don't know about the point release. I really do think we should be
doing coordinated releases; if not, it's burden to everyone else when
there's a bug reported that we have hunt down if it was fixed in one
version but not another.  That's my take at least.

Maybe we should proceed as John mentioned and just do a 6.07,
considering 6.06 was never released?  Release notes for 6.07 would
have to append the 6.06 information.

On Mon, Nov 9, 2015 at 6:26 PM, Michael Gogins  wrote:
> The WIndows release is a big pain for everyone, especially me. I will
> be ecstatic when an automatic system cross-compiles it on Linux with
> all the current features. In the meantime, to accommodate the
> difficulties, I suggest that I skip the Windows installer for version
> 6.06.0, but go right ahead and release a point version of the Windows
> installer, 6.06.1, in a few days.
>
> The only remaining issue is getting Android Studio and its version of
> the NDK to build the CsoundApplication so it will run on both Android
> 4.4 and more recent versions. Of course this is not a Windows issue,
> but I have always done the Android application release and the Windows
> release as part of the general release process.
>
> Then for 6.07.0 I should be able to easily do both releases again
> since I have already done most of the hard work, 6.0.5 was quite easy.
>
> How does that sound?
>
> Regards,,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Mon, Nov 9, 2015 at 3:02 PM, Victor Lazzarini
>  wrote:
>> So we will not have a 6.06 for Windows?
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>>> On 9 Nov 2015, at 19:56, Steven Yi  wrote:
>>>
>>> I've finished the 6.06.0 release branch. Changes have been merged into
>>> master and develop.
>>>
>>> 6.07 makes sense.  For Windows, I do not think releases for that
>>> platform should be out of sync and use commits outside of the ones
>>> used for other platforms.  It makes it difficult to track bugs
>>> introduced/fixed per version released.
>>>
>>> For moving forward, I think we should move the Windows build to be
>>> fully automated, same as it is for OSX, Linux, Android, iOS, Web, etc.
>>> The lag time and mismatching of versions is not good, IMO.
>>>
>>> steven
>>>
>>>> On Mon, Nov 9, 2015 at 10:41 AM, jpff  wrote: