devel-versioning.rst
changeset 1097 6acae85ed54b
parent 1059 d5b0b9cc4b49
child 1098 db420d971363
equal deleted inserted replaced
1096:6b89ccc3d36a 1097:6acae85ed54b
    28   http://www.cygwin.com/ml/gdb/2007-07/msg00061.html
    28   http://www.cygwin.com/ml/gdb/2007-07/msg00061.html
    29 
    29 
    30 There discussed:
    30 There discussed:
    31 
    31 
    32  * Is it essential to update major version if significant change made for
    32  * Is it essential to update major version if significant change made for
    33    licence? Answer: NO!
    33    licence? Answer: **NO**!
    34 
    34 
    35    GPLv3 is a big deal spread out over the whole GNU project, but not a big deal
    35    GPLv3 is a big deal spread out over the whole GNU project, but not a big deal
    36    for GDB in particular.
    36    for GDB in particular.
    37  * Is it right follow date version schema regardless major changes? Answer: NO!
    37  * Is it right follow date version schema regardless major changes? Answer:
       
    38    **NO**!
    38 
    39 
    39    Many OS distribution encode year in versions but versions does not present
    40    Many OS distribution encode year in versions but versions does not present
    40    featureset but package set instead.
    41    featureset but package set instead.
    41 
    42 
    42 Year as version name.
    43 Year as version name.
   159 Don't update version without human decision.
   160 Don't update version without human decision.
   160 
   161 
   161 Why do not do this on success build:
   162 Why do not do this on success build:
   162 
   163 
   163  * You can have several build machine which may concurrently update version.
   164  * You can have several build machine which may concurrently update version.
   164  * There not exist tools for easy querying for status of build (as ok/fail,
   165  * There does not exist tools for easy querying for status of build (as ok/fail,
   165    build configuration, date, coverage, lint checks, etc).
   166    build configuration, date, coverage, lint checks, etc).
   166  * Some part of development team may not have permission for bumping version and
   167  * Some part of development team may not have permission for bumping version and
   167    after build they must revert some automatically updated files.
   168    after build they must revert some automatically updated files.
   168 
   169 
   169 Why do not do this from pre-/post-commit hooks:
   170 Why do not do this from pre-/post-commit hooks: