Changes between Version 2 and Version 3 of SvnGuidelines


Ignore:
Timestamp:
11/11/14 12:56:28 (11 years ago)
Author:
dneise
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SvnGuidelines

    v2 v3  
    3232I like to define a release version of analysis software a version, that the FACT collaboration has a certain degree of confidence in. This confidence is based mostly on tests, but in special cases can also be based on the amount of care that has been taken during development. (See "What is a test?")
    3333
    34 So far the FACT collaboration did not create any released versions, at least not literally, but implicitely there have always been versions of code, that were more often used than others. These versions often had names like "Mars.von.Thomas.20yy.mm.dd" and where used to create plots for conferences and the like. I think, using a certain version of code to produce plots for a conference expresses a large amount of confidence, enough to call this version a release version.
    35 
    36 For more information about how to create new release versions of our software please refer to "How to make a new release?" further down.
     34So far the FACT collaboration did not create any released versions, at least not literally, but implicitely there have always been versions of code, that were more often used than others. These versions often had names like "Mars.von.Thomas.20yy.mm.dd" and were used to create plots for conferences and the like. I think, using a certain version of code to produce plots for a conference expresses a large amount of confidence, enough to call this version a release version.
    3735
    3836=== Why do you explain the term 'All' to us? ===