Project

General

Profile

Repository » History » Version 42

Simó Albert i Beltran, 06/09/2013 05:46 PM

1 40 Simó Albert i Beltran
h1. Repository workflow
2 35 Simó Albert i Beltran
3 1 Pau Escrich
h2. Structure
4 1 Pau Escrich
5 1 Pau Escrich
The qMp git repository is split in three branches:
6 1 Pau Escrich
7 1 Pau Escrich
# Master
8 1 Pau Escrich
# Testing
9 23 Simó Albert i Beltran
# Other: Features/Bugfixes
10 1 Pau Escrich
11 1 Pau Escrich
h3. Master
12 1 Pau Escrich
13 1 Pau Escrich
This is the main branch and all changes committed here must be tested in Testing branch before.
14 1 Pau Escrich
15 6 Simó Albert i Beltran
However the small bugfixes can be directly applied here. These changes must be merged in the testing branch.
16 1 Pau Escrich
17 10 Simó Albert i Beltran
<pre>
18 10 Simó Albert i Beltran
o---o---o---o---o master
19 10 Simó Albert i Beltran
                 \  
20 10 Simó Albert i Beltran
--o---o---o---o---o testing 
21 10 Simó Albert i Beltran
</pre>
22 10 Simó Albert i Beltran
23 22 Simó Albert i Beltran
*Example:*
24 30 Anonymous
<pre><code class="shell">
25 32 Simó Albert i Beltran
git checkout origin/testing
26 32 Simó Albert i Beltran
git merge origin/master
27 29 Simó Albert i Beltran
</code></pre>
28 22 Simó Albert i Beltran
29 22 Simó Albert i Beltran
30 1 Pau Escrich
h3. Testing
31 1 Pau Escrich
32 8 Simó Albert i Beltran
This is the branch for test new features and changes. The features must be already working features tested before in a specific branch by at least the developer. A feature can be committed here only when it is finished, but not in a middle state.
33 1 Pau Escrich
34 41 Simó Albert i Beltran
When the testing branch are deeply tested by more than one developer, than it can be merged on the master branch. Each developer can specify the commit that he thinks is a candidate to merge in master with a signed tag.
35 11 Simó Albert i Beltran
36 11 Simó Albert i Beltran
<pre>
37 11 Simó Albert i Beltran
o---o---o---o---o master
38 11 Simó Albert i Beltran
     \         /  
39 11 Simó Albert i Beltran
--o---o---o---o testing 
40 11 Simó Albert i Beltran
</pre>
41 11 Simó Albert i Beltran
42 16 Pau Escrich
*Example:*
43 11 Simó Albert i Beltran
44 16 Pau Escrich
Import master bugfixes to testing
45 30 Anonymous
<pre><code class="shell">
46 32 Simó Albert i Beltran
git checkout origin/testing
47 32 Simó Albert i Beltran
git merge origin/master
48 29 Simó Albert i Beltran
</code></pre>
49 16 Pau Escrich
50 16 Pau Escrich
Merge testing changes in master
51 30 Anonymous
<pre><code class="shell">
52 1 Pau Escrich
git checkout origin/master
53 41 Simó Albert i Beltran
git merge origin/testing
54 41 Simó Albert i Beltran
</code></pre>
55 41 Simó Albert i Beltran
56 41 Simó Albert i Beltran
Add a signed tag
57 41 Simó Albert i Beltran
<pre><code class="shell">
58 41 Simó Albert i Beltran
git tag -s master_candidate_mynick -m "Proposal to update master branch by MyName."
59 41 Simó Albert i Beltran
git push origin master_candidate_mynick
60 29 Simó Albert i Beltran
</code></pre>
61 16 Pau Escrich
62 12 Simó Albert i Beltran
h3. Other: Features/Bugfixes
63 1 Pau Escrich
64 8 Simó Albert i Beltran
The rest of the branches are temporal branches.
65 8 Simó Albert i Beltran
66 26 Simó Albert i Beltran
h4. Features
67 26 Simó Albert i Beltran
68 34 Simó Albert i Beltran
If it is about a new feature the name of the branch must be the name of the feature (of some name which identifies it). These branches are considered non-functional, so a non-finished feature can be committed here. This branch should preferably be based on a commit of master branch. Once the feature is finish and tested by at least the developer, it should be merged to testing and other branches.
69 1 Pau Escrich
70 9 Simó Albert i Beltran
<pre>
71 9 Simó Albert i Beltran
o---o---o---o---o master
72 14 Simó Albert i Beltran
     \
73 9 Simó Albert i Beltran
      o---o---o issue#23-new-feature
74 14 Simó Albert i Beltran
               \
75 9 Simó Albert i Beltran
o---o---o---o---o testing 
76 9 Simó Albert i Beltran
</pre>
77 9 Simó Albert i Beltran
78 16 Pau Escrich
*Example:*
79 9 Simó Albert i Beltran
80 30 Anonymous
<pre><code class="shell">
81 24 Simó Albert i Beltran
git checkout -b issue#23-new-feature origin/master
82 24 Simó Albert i Beltran
editor dir/file
83 25 Simó Albert i Beltran
git add dir/file
84 24 Simó Albert i Beltran
git commit
85 24 Simó Albert i Beltran
#test issue#23-new-feature branch
86 32 Simó Albert i Beltran
git checkout origin/testing
87 24 Simó Albert i Beltran
git merge issue#23-new-feature
88 29 Simó Albert i Beltran
</code></pre>
89 24 Simó Albert i Beltran
90 27 Simó Albert i Beltran
h4. Bugfixes
91 24 Simó Albert i Beltran
92 33 Simó Albert i Beltran
A bugfix must be implemented in a new branch. This branch must be based on a commit of the master branch. This branch should not be based on a commit of the testing branch because it may contain new features and these maybe cannot be imported in the master branch. This new branch can be merged in testing and other branches.
93 7 Simó Albert i Beltran
94 7 Simó Albert i Beltran
<pre>
95 7 Simó Albert i Beltran
o---o---o---o---o master
96 1 Pau Escrich
     \         /
97 9 Simó Albert i Beltran
      o---o---o issue#23-bugfix
98 7 Simó Albert i Beltran
               \
99 7 Simó Albert i Beltran
o---o---o---o---o testing 
100 7 Simó Albert i Beltran
</pre>
101 16 Pau Escrich
102 16 Pau Escrich
*Example:*
103 1 Pau Escrich
104 30 Anonymous
<pre><code class="shell">
105 28 Simó Albert i Beltran
git checkout -b issue#23-bugfix origin/master
106 28 Simó Albert i Beltran
editor dir/file
107 28 Simó Albert i Beltran
git add dir/file
108 28 Simó Albert i Beltran
git commit
109 28 Simó Albert i Beltran
#test issue#23-bugfix branch
110 28 Simó Albert i Beltran
git checkout origin/testing
111 28 Simó Albert i Beltran
git merge issue#23-bugfix
112 28 Simó Albert i Beltran
git checkout origin/master
113 28 Simó Albert i Beltran
git merge issue#23-bugfix
114 29 Simó Albert i Beltran
</code></pre>
115 28 Simó Albert i Beltran
116 28 Simó Albert i Beltran
117 1 Pau Escrich
h2. How to use it
118 1 Pau Escrich
119 2 Pau Escrich
120 2 Pau Escrich
h2. Good practices