Changes between Version 1 and Version 2 of SvnGuidelines
- Timestamp:
- 11/11/14 12:07:36 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SvnGuidelines
v1 v2 3 3 = FACT, Mars, SVN, agreement, stuff = 4 4 5 The members of the fact collaboration agree, that they actually want to collaborate on FACT software development in a way that is both orderly and lighning fast. 6 7 ---- 8 5 //The members of the fact collaboration agree, that they actually want to collaborate on FACT software development in a way that is both orderly and lightning fast.// 9 6 10 7 Welcome! … … 15 12 16 13 * All software 'fact' uses, is (the most recent) release version. 17 * The trunk is * the* development version.14 * The trunk is **the** development version. 18 15 19 16 Withing the following paragraphs I will elaborate a bit. … … 45 42 ---- 46 43 47 == The trunk is * the* development version. ==44 == The trunk is **the** development version. == 48 45 49 46 This guideline can be seen as an invitation and a warning at the same time. First of all it is an invitation. Everybody is not only welcome to contribute with software development, but actually expected to. Additional features may be commited directly into the trunk, after they have been anounced by creating a ticket. (please refer to the next paragraph to learn why one should create a ticket) … … 74 71 No, simple refactoring of the code base does not need to be set into a larger context. 75 72 73 == Tests? == 74 From other software projects you are certainly be used to having a quite complete test coverage. This is neither the case for Mars nor FACT++. We are just starting to implement some tests using the gtest framework (Sebastian). 76 75 77 == Tests? == 78 From other software projects you are certainly be used to having a quite complete test coverage. This is neither the case for Mars nor FACT++. In fact we have no idea how to provide any means of unit test coverage for these. 79 But fear not, we still can do regression tests to see, if something we changed recently alters the end result in an unexpected way. Currently there are no regression tests set up for you, but I strongly recommend to start setting up a few asap. 80 81 82 83 == Who decides, when to create a new release? == 84 --> Question about maintainance. 76 But fear not, even when the unit test ceverage is fairly low, we still can do integration tests to see, if something we changed recently alters the end result in an unexpected way.
