Hi All,

I was emailing with Victor and it seems like we're pretty close to do
the 6.06.0 release.  Just a reminder on the process:

- I'll setup a release branch called release/6.06.0
- version numbers will be updated in that branch for 6.06.0
- We can then do builds for installers and releases.  Any last minute
changes for installers and what not should go into the release branch.
- When we're complete with building the installers/releases, I'll
"finish" (using git-flow terminology) the release and that will tag
and merge changes back into master and develop.

I think right now there are few outstanding issues:

- https://github.com/csound/csound/issues/526  - this has to do with
building on Arch with a newer glibc.  I think this should get
addressed with Cmake changes as mentioned on that issue.  Just waiting
to get confirmation on the remaining issue with csound-bin.  If that's
all that's left, we can make changes to CMake and complete that issue.

- https://github.com/csound/csound/issues/508 - this is for releasing
Csound for Android as an AAR archive file on JCenter.  This can be
done separately from the main release; for 6.06.0, the build is ready
to go for the main ZIP release of Csound for Android.

- https://github.com/csound/csound/issues/482 - This is for Csound for
iOS.  I got stuck on getting the dynamic framework working and had to
stop for the moment to work on other things.  I'm proposing we release
a 6.06.0-iOS release after the main 6.06 release, that will get tagged
and all that separately (done in a hotfix branch).  We could also do
one more static library release for 6.06, then release this as soon as
it is working.

Please chime in on any other concerns or issues.  Otherwise, I'll plan
to start the release branch tomorrow.

Thanks!
steven

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

hi dear uploaders -

just as a sidenote:  can we have a better structure in the sourceforge 
download folder?  i think (and experienced) it is currently very hard 
for non-experienced csound users to find the correct version.  my 
suggestion is to have these subfolders in the 6.06 folder:

Android
iOS
Linux (or Sources)
MaxMSP
OSX
Web (pnacl, emscripten)
Windows

i think something like this would be a huge improvement for many people 
getting there.

best -
	joachim


On 26/09/15 02:33, Steven Yi wrote:
> Hi All,
>
> I was emailing with Victor and it seems like we're pretty close to do
> the 6.06.0 release.  Just a reminder on the process:
>
> - I'll setup a release branch called release/6.06.0
> - version numbers will be updated in that branch for 6.06.0
> - We can then do builds for installers and releases.  Any last minute
> changes for installers and what not should go into the release branch.
> - When we're complete with building the installers/releases, I'll
> "finish" (using git-flow terminology) the release and that will tag
> and merge changes back into master and develop.
>
> I think right now there are few outstanding issues:
>
> - https://github.com/csound/csound/issues/526  - this has to do with
> building on Arch with a newer glibc.  I think this should get
> addressed with Cmake changes as mentioned on that issue.  Just waiting
> to get confirmation on the remaining issue with csound-bin.  If that's
> all that's left, we can make changes to CMake and complete that issue.
>
> - https://github.com/csound/csound/issues/508 - this is for releasing
> Csound for Android as an AAR archive file on JCenter.  This can be
> done separately from the main release; for 6.06.0, the build is ready
> to go for the main ZIP release of Csound for Android.
>
> - https://github.com/csound/csound/issues/482 - This is for Csound for
> iOS.  I got stuck on getting the dynamic framework working and had to
> stop for the moment to work on other things.  I'm proposing we release
> a 6.06.0-iOS release after the main 6.06 release, that will get tagged
> and all that separately (done in a hotfix branch).  We could also do
> one more static library release for 6.06, then release this as soon as
> it is working.
>
> Please chime in on any other concerns or issues.  Otherwise, I'll plan
> to start the release branch tomorrow.
>
> Thanks!
> steven
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi All,

So I'm finding the issue that ainola reported to be quite odd.  A
number of the linking issues all relate to the pow function in libm,
but libm should be linked to in libcsound.so.  Also, a number of the
executables with linking errors that have source code files that do
not even use pow.

The fix that is currently explored is adding:

target_link_libraries(__TARGET_NAME___  m)

for each target that happens to cause a problem. However, the solution
by the end seems to add libm to almost every target, which makes me
think there should be a better solution to all of this.

I'd like to either hold off on the release to address the above in a
better way than what is in the ticket
(https://github.com/csound/csound/issues/526), or we punt on this and
move on with the release.  For the short term though, I will look into
seeing if I can get an Arch VM setup (last time I tried that though, I
was not very successful...)

steven

On Sat, Sep 26, 2015 at 3:01 PM, Steven Yi  wrote:
> Hi Joachim,
>
> I thought we were using the README to explain to users what download to
> choose?
>
> Side note: I'm in the middle of moving and hopefully should have internet
> set back up tomorrow. I'll set up the release branch tomorrow then.
>
> Steven
>
> On Sat, Sep 26, 2015 at 12:31 PM joachim heintz  wrote:
>>
>> hi dear uploaders -
>>
>> just as a sidenote:  can we have a better structure in the sourceforge
>> download folder?  i think (and experienced) it is currently very hard
>> for non-experienced csound users to find the correct version.  my
>> suggestion is to have these subfolders in the 6.06 folder:
>>
>> Android
>> iOS
>> Linux (or Sources)
>> MaxMSP
>> OSX
>> Web (pnacl, emscripten)
>> Windows
>>
>> i think something like this would be a huge improvement for many people
>> getting there.
>>
>> best -
>>         joachim
>>
>>
>> On 26/09/15 02:33, Steven Yi wrote:
>> > Hi All,
>> >
>> > I was emailing with Victor and it seems like we're pretty close to do
>> > the 6.06.0 release.  Just a reminder on the process:
>> >
>> > - I'll setup a release branch called release/6.06.0
>> > - version numbers will be updated in that branch for 6.06.0
>> > - We can then do builds for installers and releases.  Any last minute
>> > changes for installers and what not should go into the release branch.
>> > - When we're complete with building the installers/releases, I'll
>> > "finish" (using git-flow terminology) the release and that will tag
>> > and merge changes back into master and develop.
>> >
>> > I think right now there are few outstanding issues:
>> >
>> > - https://github.com/csound/csound/issues/526  - this has to do with
>> > building on Arch with a newer glibc.  I think this should get
>> > addressed with Cmake changes as mentioned on that issue.  Just waiting
>> > to get confirmation on the remaining issue with csound-bin.  If that's
>> > all that's left, we can make changes to CMake and complete that issue.
>> >
>> > - https://github.com/csound/csound/issues/508 - this is for releasing
>> > Csound for Android as an AAR archive file on JCenter.  This can be
>> > done separately from the main release; for 6.06.0, the build is ready
>> > to go for the main ZIP release of Csound for Android.
>> >
>> > - https://github.com/csound/csound/issues/482 - This is for Csound for
>> > iOS.  I got stuck on getting the dynamic framework working and had to
>> > stop for the moment to work on other things.  I'm proposing we release
>> > a 6.06.0-iOS release after the main 6.06 release, that will get tagged
>> > and all that separately (done in a hotfix branch).  We could also do
>> > one more static library release for 6.06, then release this as soon as
>> > it is working.
>> >
>> > Please chime in on any other concerns or issues.  Otherwise, I'll plan
>> > to start the release branch tomorrow.
>> >
>> > Thanks!
>> > steven
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi All,

I managed to get Arch setup in a VM and applied a fix for #526.  I
have gone ahead and setup the release/6.06.0 branch which is now on
github. You can pull that branch by using:

git pull
git checkout release/6.06.0

I have also updated version numbers for ones that I found.  I will
work on the Android and Emscripten builds now.  I have also gone ahead
and created the 6.06 folder on Sourceforge and marked it as staged (I
figured John and Victor may be asleep by now.)

Thanks!
steven

On Mon, Sep 28, 2015 at 10:52 AM, Steven Yi  wrote:
> Hi All,
>
> So I'm finding the issue that ainola reported to be quite odd.  A
> number of the linking issues all relate to the pow function in libm,
> but libm should be linked to in libcsound.so.  Also, a number of the
> executables with linking errors that have source code files that do
> not even use pow.
>
> The fix that is currently explored is adding:
>
> target_link_libraries(__TARGET_NAME___  m)
>
> for each target that happens to cause a problem. However, the solution
> by the end seems to add libm to almost every target, which makes me
> think there should be a better solution to all of this.
>
> I'd like to either hold off on the release to address the above in a
> better way than what is in the ticket
> (https://github.com/csound/csound/issues/526), or we punt on this and
> move on with the release.  For the short term though, I will look into
> seeing if I can get an Arch VM setup (last time I tried that though, I
> was not very successful...)
>
> steven
>
> On Sat, Sep 26, 2015 at 3:01 PM, Steven Yi  wrote:
>> Hi Joachim,
>>
>> I thought we were using the README to explain to users what download to
>> choose?
>>
>> Side note: I'm in the middle of moving and hopefully should have internet
>> set back up tomorrow. I'll set up the release branch tomorrow then.
>>
>> Steven
>>
>> On Sat, Sep 26, 2015 at 12:31 PM joachim heintz  wrote:
>>>
>>> hi dear uploaders -
>>>
>>> just as a sidenote:  can we have a better structure in the sourceforge
>>> download folder?  i think (and experienced) it is currently very hard
>>> for non-experienced csound users to find the correct version.  my
>>> suggestion is to have these subfolders in the 6.06 folder:
>>>
>>> Android
>>> iOS
>>> Linux (or Sources)
>>> MaxMSP
>>> OSX
>>> Web (pnacl, emscripten)
>>> Windows
>>>
>>> i think something like this would be a huge improvement for many people
>>> getting there.
>>>
>>> best -
>>>         joachim
>>>
>>>
>>> On 26/09/15 02:33, Steven Yi wrote:
>>> > Hi All,
>>> >
>>> > I was emailing with Victor and it seems like we're pretty close to do
>>> > the 6.06.0 release.  Just a reminder on the process:
>>> >
>>> > - I'll setup a release branch called release/6.06.0
>>> > - version numbers will be updated in that branch for 6.06.0
>>> > - We can then do builds for installers and releases.  Any last minute
>>> > changes for installers and what not should go into the release branch.
>>> > - When we're complete with building the installers/releases, I'll
>>> > "finish" (using git-flow terminology) the release and that will tag
>>> > and merge changes back into master and develop.
>>> >
>>> > I think right now there are few outstanding issues:
>>> >
>>> > - https://github.com/csound/csound/issues/526  - this has to do with
>>> > building on Arch with a newer glibc.  I think this should get
>>> > addressed with Cmake changes as mentioned on that issue.  Just waiting
>>> > to get confirmation on the remaining issue with csound-bin.  If that's
>>> > all that's left, we can make changes to CMake and complete that issue.
>>> >
>>> > - https://github.com/csound/csound/issues/508 - this is for releasing
>>> > Csound for Android as an AAR archive file on JCenter.  This can be
>>> > done separately from the main release; for 6.06.0, the build is ready
>>> > to go for the main ZIP release of Csound for Android.
>>> >
>>> > - https://github.com/csound/csound/issues/482 - This is for Csound for
>>> > iOS.  I got stuck on getting the dynamic framework working and had to
>>> > stop for the moment to work on other things.  I'm proposing we release
>>> > a 6.06.0-iOS release after the main 6.06 release, that will get tagged
>>> > and all that separately (done in a hotfix branch).  We could also do
>>> > one more static library release for 6.06, then release this as soon as
>>> > it is working.
>>> >
>>> > Please chime in on any other concerns or issues.  Otherwise, I'll plan
>>> > to start the release branch tomorrow.
>>> >
>>> > Thanks!
>>> > steven
>>> >
>>> >
>>> > ------------------------------------------------------------------------------
>>> > _______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net