Are giving the develop branch scheme a go? If so, once 6.00.1 gets tagged we should move all development work to a develop branch and leave the master untouched.
Is there a develop branch already in the repo? If not let's start one.

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

As the manual has been built as 6.01 I am going to stick to that number
for this cycle.

If we are going to try the develop branch then please can someone give me
instructions!  I have a difficult relationship with git but have a
collection of scripts to make it barable that may need adjustment.

I will tag in a short while

==John

> Are giving the develop branch scheme a go? If so, once 6.00.1 gets tagged
> we should move all development work to a develop branch and leave the
> master untouched.
> Is there a develop branch already in the repo? If not let's start one.
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>



------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Once we have it setup, you can just do

$ git checkout develop 

and then work as normal from there.

when we are ready to release, one of us merges the develop branch into the
master branch and we use it to build the next release.

Victor
On 5 Aug 2013, at 10:48, jpff@cs.bath.ac.uk wrote:

> As the manual has been built as 6.01 I am going to stick to that number
> for this cycle.
> 
> If we are going to try the develop branch then please can someone give me
> instructions!  I have a difficult relationship with git but have a
> collection of scripts to make it barable that may need adjustment.
> 
> I will tag in a short while
> 
> ==John
> 
>> Are giving the develop branch scheme a go? If so, once 6.00.1 gets tagged
>> we should move all development work to a develop branch and leave the
>> master untouched.
>> Is there a develop branch already in the repo? If not let's start one.
>> 
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
>> 
>> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent 
> caught up. So what steps can you take to put your SQL databases under 
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think the general wish was for 6.00.1 but I do not mind much.  There are
only minimal new opcodes -- mainly adjustments to array operations.  I
need to check what else changed.

==John

> I built the manual as 6.01 because this was the number used in one of
> John's last mail. If people prefer 6.00.1, I can rebuild the manual as
> 6.00.1. Any way, this could be the occasion to add a 'Release Notes for
> Csound6' based on John's mail from July 9th.
>
> I'll have some time this evening. Please let me know if you want to change
> the version number to 6.00.1 and if Release notes can be added as it is.
>
> Regards
>
> Francois
>
>
> 2013/8/5 
>
>> As the manual has been built as 6.01 I am going to stick to that number
>> for this cycle.
>>
>> If we are going to try the develop branch then please can someone give
>> me
>> instructions!  I have a difficult relationship with git but have a
>> collection of scripts to make it barable that may need adjustment.
>>
>> I will tag in a short while
>>
>> ==John
>>
>> > Are giving the develop branch scheme a go? If so, once 6.00.1 gets
>> tagged
>> > we should move all development work to a develop branch and leave the
>> > master untouched.
>> > Is there a develop branch already in the repo? If not let's start one.
>> >
>> > Dr Victor Lazzarini
>> > Senior Lecturer
>> > Dept. of Music
>> > NUI Maynooth Ireland
>> > tel.: +353 1 708 3545
>> > Victor dot Lazzarini AT nuim dot ie
>> >
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Get your SQL database under version control now!
>> > Version control is standard for application code, but databases havent
>> > caught up. So what steps can you take to put your SQL databases under
>> > version control? Why should you start doing it? Read more to find out.
>> >
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> >
>> >
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

If there are new additions (opcodes etc), then it should be 6.01, IMHO.

On 5 Aug 2013, at 11:40, jpff@cs.bath.ac.uk wrote:

> I think the general wish was for 6.00.1 but I do not mind much.  There are
> only minimal new opcodes -- mainly adjustments to array operations.  I
> need to check what else changed.
> 
> ==John
> 
>> I built the manual as 6.01 because this was the number used in one of
>> John's last mail. If people prefer 6.00.1, I can rebuild the manual as
>> 6.00.1. Any way, this could be the occasion to add a 'Release Notes for
>> Csound6' based on John's mail from July 9th.
>> 
>> I'll have some time this evening. Please let me know if you want to change
>> the version number to 6.00.1 and if Release notes can be added as it is.
>> 
>> Regards
>> 
>> Francois
>> 
>> 
>> 2013/8/5 
>> 
>>> As the manual has been built as 6.01 I am going to stick to that number
>>> for this cycle.
>>> 
>>> If we are going to try the develop branch then please can someone give
>>> me
>>> instructions!  I have a difficult relationship with git but have a
>>> collection of scripts to make it barable that may need adjustment.
>>> 
>>> I will tag in a short while
>>> 
>>> ==John
>>> 
>>>> Are giving the develop branch scheme a go? If so, once 6.00.1 gets
>>> tagged
>>>> we should move all development work to a develop branch and leave the
>>>> master untouched.
>>>> Is there a develop branch already in the repo? If not let's start one.
>>>> 
>>>> Dr Victor Lazzarini
>>>> Senior Lecturer
>>>> Dept. of Music
>>>> NUI Maynooth Ireland
>>>> tel.: +353 1 708 3545
>>>> Victor dot Lazzarini AT nuim dot ie
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> ------------------------------------------------------------------------------
>>>> Get your SQL database under version control now!
>>>> Version control is standard for application code, but databases havent
>>>> caught up. So what steps can you take to put your SQL databases under
>>>> version control? Why should you start doing it? Read more to find out.
>>>> 
>>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Get your SQL database under version control now!
>>> Version control is standard for application code, but databases havent
>>> caught up. So what steps can you take to put your SQL databases under
>>> version control? Why should you start doing it? Read more to find out.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> 
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent 
> caught up. So what steps can you take to put your SQL databases under 
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

There opcodes are
New:    signum
        genarray_i

Major change
        genarray

Hardly worth a version bump

> If there are new additions (opcodes etc), then it should be 6.01, IMHO.
>
> On 5 Aug 2013, at 11:40, jpff@cs.bath.ac.uk wrote:
>
>> I think the general wish was for 6.00.1 but I do not mind much.  There
>> are
>> only minimal new opcodes -- mainly adjustments to array operations.  I
>> need to check what else changed.
>>
>> ==John
>>
>>> I built the manual as 6.01 because this was the number used in one of
>>> John's last mail. If people prefer 6.00.1, I can rebuild the manual as
>>> 6.00.1. Any way, this could be the occasion to add a 'Release Notes for
>>> Csound6' based on John's mail from July 9th.
>>>
>>> I'll have some time this evening. Please let me know if you want to
>>> change
>>> the version number to 6.00.1 and if Release notes can be added as it
>>> is.
>>>
>>> Regards
>>>
>>> Francois
>>>
>>>
>>> 2013/8/5 
>>>
>>>> As the manual has been built as 6.01 I am going to stick to that
>>>> number
>>>> for this cycle.
>>>>
>>>> If we are going to try the develop branch then please can someone give
>>>> me
>>>> instructions!  I have a difficult relationship with git but have a
>>>> collection of scripts to make it barable that may need adjustment.
>>>>
>>>> I will tag in a short while
>>>>
>>>> ==John
>>>>
>>>>> Are giving the develop branch scheme a go? If so, once 6.00.1 gets
>>>> tagged
>>>>> we should move all development work to a develop branch and leave the
>>>>> master untouched.
>>>>> Is there a develop branch already in the repo? If not let's start
>>>>> one.
>>>>>
>>>>> Dr Victor Lazzarini
>>>>> Senior Lecturer
>>>>> Dept. of Music
>>>>> NUI Maynooth Ireland
>>>>> tel.: +353 1 708 3545
>>>>> Victor dot Lazzarini AT nuim dot ie
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

ad there is a (staged) directory Csound6.00.1 to receive systems

I will upload sources next

==John


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi John,

Just got back from the country side and catching up on emails. I've
gone ahead and made a develop branch and pushed it to Sourceforge.
It's branched from master.  I'll write up an email in a moment
explaining steps to take and start a new thread.

Thanks!
steven

On Mon, Aug 5, 2013 at 11:48 AM,   wrote:
> As the manual has been built as 6.01 I am going to stick to that number
> for this cycle.
>
> If we are going to try the develop branch then please can someone give me
> instructions!  I have a difficult relationship with git but have a
> collection of scripts to make it barable that may need adjustment.
>
> I will tag in a short while
>
> ==John
>
>> Are giving the develop branch scheme a go? If so, once 6.00.1 gets tagged
>> we should move all development work to a develop branch and leave the
>> master untouched.
>> Is there a develop branch already in the repo? If not let's start one.
>>
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Mon, Aug 5, 2013 at 5:48 AM,   wrote:
> I have a difficult relationship with git but have a
> collection of scripts to make it barable that may need adjustment.

Please report the issues you are facing to the list! I still don't
understand the issues you are facing, and I'm quite optimistic that we
can sort them out. I sure would be glad to help if I can.

Having to fight the version control system can be a real PITA, which
is why git itself was created! It is quite ironic that it has become a
source of frustration.


-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I've uploaded OSX 10.8, Android, and iOS.  I've also updated the
Homebrew tap for OSX for 6.00.1.

On Mon, Aug 5, 2013 at 2:19 PM,   wrote:
> ad there is a (staged) directory Csound6.00.1 to receive systems
>
> I will upload sources next
>
> ==John
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net