January 24, 2011 at 04:06Books // Software Configuration Management Templates
Kind.
Recently, he began reading and reviewing books on his favorite topic - SCM, which primarily includes version control, change tracking, tuning and release releases, and several other equally important topics. This time one more book from among those that I chose for detailed acquaintance came under the distribution . Called Software Configuration Management Patterns : Effective Teamwork, Practical Integration, authors - Stephen P. Berczuk and Brad Appleton. It can be translated into Russian as “Software configuration management templates: Effective team work, practical integration.”
As in any other field of knowledge, SCM has its own well-established practices, techniques, and simply successful ways to make work effective. Accordingly, someone should have already arranged all this in one source. The authors, however, have extensive experience not only in software development, but also in configuration management, so it was they who took up the task.
The theme of patterns in the development of software has been worked out for quite some time. Moreover, as it turned out, it takes its beginning from architecture. Sergey Teplyakov not so long ago told on the pages of RSDN Magazine about the origins of this trend, read (after this note, of course).
The whole book is divided into the introductory part, 2 main sections and a couple of applications.
The introduction and the entire 1st section briefly remind the reader what Software Configuration Management is and what templates are. What is noteworthy - here is not just a first-person narration, but quotes from many other works. Authors often publish in magazines and participate in conferences. Therefore, there is no shortage of references to themselves or to other industry authorities. In general, a normal scientific approach, it is immediately obvious that it is not just taken from the head, but also at least thought over by other people.
The basis of the book is, of course, a description of the templates themselves. Each template is given in the same way - the problem situation is described and questions are asked about further actions, then a detailed answer is given. After that, tasks that are associated with the described template, but have not yet been resolved (Unresolved issues) are noted, as well as links to the literature where you can read about the described techniques in more detail (Further reading). In general, the right engineering approach.
A total of 16 patterns are described , which the authors conditionally divide into 2 sets.
First is Codeline-related patterns , i.e. those templates that show how to work with the code. These include:
The second set is Workspace-related patterns , where they go:
In general, the basic practices that many have heard or tried about.
The remaining applications give brief descriptions of useful resources on SCM and basic tools (however, here the information is somewhat outdated).
The overall result - I want more templates, but already in this form it is a good reference on the right techniques, we must take it.
Recently, he began reading and reviewing books on his favorite topic - SCM, which primarily includes version control, change tracking, tuning and release releases, and several other equally important topics. This time one more book from among those that I chose for detailed acquaintance came under the distribution . Called Software Configuration Management Patterns : Effective Teamwork, Practical Integration, authors - Stephen P. Berczuk and Brad Appleton. It can be translated into Russian as “Software configuration management templates: Effective team work, practical integration.”
As in any other field of knowledge, SCM has its own well-established practices, techniques, and simply successful ways to make work effective. Accordingly, someone should have already arranged all this in one source. The authors, however, have extensive experience not only in software development, but also in configuration management, so it was they who took up the task.
The theme of patterns in the development of software has been worked out for quite some time. Moreover, as it turned out, it takes its beginning from architecture. Sergey Teplyakov not so long ago told on the pages of RSDN Magazine about the origins of this trend, read (after this note, of course).
The whole book is divided into the introductory part, 2 main sections and a couple of applications.
The introduction and the entire 1st section briefly remind the reader what Software Configuration Management is and what templates are. What is noteworthy - here is not just a first-person narration, but quotes from many other works. Authors often publish in magazines and participate in conferences. Therefore, there is no shortage of references to themselves or to other industry authorities. In general, a normal scientific approach, it is immediately obvious that it is not just taken from the head, but also at least thought over by other people.
The basis of the book is, of course, a description of the templates themselves. Each template is given in the same way - the problem situation is described and questions are asked about further actions, then a detailed answer is given. After that, tasks that are associated with the described template, but have not yet been resolved (Unresolved issues) are noted, as well as links to the literature where you can read about the described techniques in more detail (Further reading). In general, the right engineering approach.
A total of 16 patterns are described , which the authors conditionally divide into 2 sets.
First is Codeline-related patterns , i.e. those templates that show how to work with the code. These include:
- Mainline - the use of the main branch for issuing stable releases and storing only stable code;
- Active development line - development on a trunk with minimal branching and active work;
- Private versions - branching for the needs of the developer, branches are used for debugging and intermediate results;
- Release line - branching with the aim of forming new releases (1 new release = 1 branch);
- Release-prep code line - the same as release line, only branching occurs immediately before release to stabilize the work;
- Task branch - branch-on-task;
- Codeline policy - implementation and maintenance of policies closely related to code commit and its (automatic) verification;
The second set is Workspace-related patterns , where they go:
- Private workspace - about the need to allocate to the developer a workspace with those versions of the code and environment settings that are needed to work;
- Repository - a repository that stores not only versions of the code, but also the tools necessary for working and creating releases;
- Private system build - about the need to enable the developer to rebuild the system without intersecting with the other project participants;
- Integration build - integration builds to combine the work of participants;
- Third-party codeline - on how to organize versioning of third-party dependencies;
- Task-level commit - variation on the theme of task branch;
- Smoke test - about automated testing at each commit to the main or active branch;
- Unit test - the same technique;
- Regression test - about the need to conduct regression testing before delivery of the delta for integration
In general, the basic practices that many have heard or tried about.
The remaining applications give brief descriptions of useful resources on SCM and basic tools (however, here the information is somewhat outdated).
The overall result - I want more templates, but already in this form it is a good reference on the right techniques, we must take it.