@@ -41,14 +41,14 @@ changes in this maintenance branch. This is important because we will later
41
41
merge the ensuing release commits up to master with ` --strategy=ours ` , which
42
42
will ignore changes from the merged commits.
43
43
44
- ## Update composer.json and CI matrices
44
+ ## Update extension requirement
45
45
46
- This is especially important before releasing a new minor version.
46
+ In ` composer.json ` , ensure that the version of ` ext-mongodb ` is correct for
47
+ the library version being released.
48
+
49
+ ## Update CI matrices
47
50
48
- Ensure that the extension requirement and branch alias in ` composer.json ` are
49
- correct for the library version being released. For example, the 1.15.0 release
50
- of the library should depend on version ` ^1.15.0 ` of the extension and master
51
- branch alias should be ` 1.15.x-dev ` .
51
+ This is especially important before releasing a new minor version.
52
52
53
53
If this is the first release of a minor version for the library, it is likely
54
54
following an extension release. The ` vars ` for calling ` compile extension ` from
@@ -90,21 +90,22 @@ After releasing a new major or minor version (e.g. 1.9.0), a maintenance branch
90
90
1.9.1) would then be done within that branch and any development for the next
91
91
major or minor release can continue in master.
92
92
93
- After creating a maintenance branch, the ` extra.branch-alias.dev-master ` field
94
- in the master branch's ` composer.json ` file should be updated. For example,
95
- after branching v1.9, ` composer.json ` in the master branch may still read:
93
+ When work begins on a major new version, create a maintenance branch for the
94
+ last minor version and update the ` extra.branch-alias.dev-master ` field
95
+ in the master branch's ` composer.json ` file. For example, after branching v1.99,
96
+ ` composer.json ` in the master branch may still read:
96
97
97
98
```
98
99
"branch-alias": {
99
- "dev-master": "1.9. x-dev"
100
+ "dev-master": "1.x-dev"
100
101
}
101
102
```
102
103
103
104
The above would be changed to:
104
105
105
106
```
106
107
"branch-alias": {
107
- "dev-master": "1.10 .x-dev"
108
+ "dev-master": "2 .x-dev"
108
109
}
109
110
```
110
111
@@ -124,24 +125,6 @@ $ git checkout -b vX.Y
124
125
$ git push mongodb vX.Y
125
126
```
126
127
127
- Update the master branch alias in ` composer.json ` :
128
-
129
- ``` diff
130
- "extra": {
131
- "branch-alias": {
132
- - "dev-master": "1.15.x-dev"
133
- + "dev-master": "1.16.x-dev"
134
- }
135
- },
136
- ```
137
-
138
- Commit and push this change:
139
-
140
- ``` console
141
- $ git commit -m " Master is now X.Y-dev" composer.json
142
- $ git push mongodb
143
- ```
144
-
145
128
### After releasing a patch version
146
129
147
130
If this was a patch release, the maintenance branch must be merged up to master:
0 commit comments