Views of baseline, Mr. Jing

Baseline meaning: one step at a time ......

Baseline is a confusing concept. Why is it easy to get confused? To put it deeper, there are cultural factors ...... Baseline is a concept commonly used by European and American people. It is far more than in the SCM field ...... Let's just say something ......

Even in the SCM field, baseline has several meanings that are slightly different from each other.

The first, most common, refersSource codeThe Snapshot (Snapshot/section) of the tree ). Of course, a snapshot at any time is baseline. Baseline usually means that, first, it is clearly identified and can be reproduced in the future. For example, it is identified by a label or tag. Secondly, it reaches a certain quality level. For example, compilation passed, or a rough test passed, or the system test passed. In this way, the baseline is like a footprint. Only when this step is implemented can we proceed to the next step ...... If the project is not big, it's refreshing and everything is under control, you can skip. However, in a large-scale project, it's better to stay stable in the dark and unknown quagmire ......

The second type refers to a document version. This version has good quality and has no errors or conflicts. The related comrades have also read and agreed, and all have their heads. This version serves as the baseline. Everyone will abide by it in the future. If it is a requirement document, do not change it easily. design it based on it. If it is a design document, it is easy not to change, it should be implemented according to it ...... Here, the baseline is a bit like getting married ...... That is to say, divorce can be done ...... Don't change it easily. You can change it as a last resort, but it is troublesome to change it. You must first obtain the unanimous consent of the relevant comrades again (generally speaking )......

The third is not a document, but a project's "all" document and "all" SourceCodeA section. This section should not only ensure a certain quality, but more importantly, 1. achieve a certain stage goal, such as system design or implementation of an important function. 2. Within the baseline, documents and source code are consistent. The document says, click the button to pull out three red-eye rabbits, the source code will be able to pull out three red-eye rabbits, four is not good, green eyes are not good, the mouse is not good ...... Generally, such baselines correspond to the milestone (milestone) of the project.

In terms of frequency. The first type of baseline is usually frequent. It may be one or two weeks, or one or two days. For the second baseline, each document may have only one or more modifications. The third type of baseline is a limited number. It is usually planned at the beginning of the project.

Write it here. Original. It is inevitable that there will be bias. For more information, please join us!

From: http://www.dongyue.name/scm/articles/scmlife/what_is_baseline.htm