Re reading the spec I agree that this is a minor version change. I
will update the patch accordingly.

Good  call by the way.

On Thu, Mar 10, 2011 at 6:19 PM, Jordan Wilberding
<[email protected]> wrote:
> Eric,
> I am CC'ing erlware-dev on this, because I would like some consensus as we
> migrate to the new semantic versioning (http://semver.org/)
> I think it might be appropriate to make this a minor change instead of a
> patch change, since we are moving to a new versioning system.
> I would suggest we think about bumping to 0.24.0
> What are the thoughts of everyone else?
> Thanks!
> Jordan Wilberding
>
> On Thu, Mar 10, 2011 at 6:56 PM, Eric Merritt <[email protected]>
> wrote:
>>
>> ---
>>  bin/sinan      |    2 +-
>>  ebin/sinan.app |    2 +-
>>  sinan.cfg      |    2 +-
>>  3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/bin/sinan b/bin/sinan
>> index 6516319..11c2915 100755
>> --- a/bin/sinan
>> +++ b/bin/sinan
>> @@ -8,7 +8,7 @@ mkdir -p $CONFIGDIR
>>
>>  #### Fill in values for these variables ####
>>  REL_NAME=sinan
>> -REL_VSN=0.23.0.0
>> +REL_VSN=0.23.1
>>  ERTS_VSN=5.8.2
>>  ###########################################
>>
>> diff --git a/ebin/sinan.app b/ebin/sinan.app
>> index c730f6e..f13846d 100644
>> --- a/ebin/sinan.app
>> +++ b/ebin/sinan.app
>> @@ -2,7 +2,7 @@
>>
>>  {application, sinan,
>>  [{description, "Build system for erlang"},
>> -  {vsn, "0.23.0.0"},
>> +  {vsn, "0.23.1"},
>>   {modules, [sin_hooks,
>>             sin_task_doc,
>>             sin_task_version,
>> diff --git a/sinan.cfg b/sinan.cfg
>> index c8b698d..41f71f0 100644
>> --- a/sinan.cfg
>> +++ b/sinan.cfg
>> @@ -1,7 +1,7 @@
>>
>>  "project" : {
>>    "name" : "sinan",
>> -   "vsn"  : "0.23.0.0"
>> +   "vsn"  : "0.23.1"
>>  },
>>
>>  "tasks" : {
>> --
>> 1.7.3.5
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"erlware-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/erlware-dev?hl=en.

Reply via email to