@@ -203,7 +203,7 @@ always refer to libmongoc.
203
203
``` shell
204
204
cd src/libmongoc
205
205
git fetch
206
- git checkout 1.20 .0
206
+ git checkout 2.1 .0
207
207
```
208
208
209
209
During development, it may be necessary to temporarily point the submodule to a
@@ -218,24 +218,16 @@ git submodules set-url src/libmongoc https://github.com/<owner>/<repo>.git
218
218
git submodules set-branch -b < branch> src/libmongoc
219
219
```
220
220
221
- #### Ensure version information is correct
221
+ #### Ensure version information is correct (libmongocrypt only)
222
222
223
- Various build processes and tools rely on the version files to infer version
224
- information. This file can be regenerated using Makefile targets:
223
+ For libmongocrypt, version information needs to be updated after updating to
224
+ a newer submodule version. This can be done by running the corresponding make
225
+ target:
225
226
226
227
``` shell
227
- make libmongoc -version-current
228
+ make libmongocrypt -version-current
228
229
```
229
230
230
- Alternatively, the ` build/calc_release_version.py ` script in the submodule can
231
- be executed directly.
232
-
233
- Note: If the submodule points to a non-release, non-master branch, the script
234
- may fail to correctly detect the version. This issue is being tracked in
235
- [ CDRIVER-3315] ( https://jira.mongodb.org/browse/CDRIVER-3315 ) and can be safely ignored since this should only happen
236
- during development (any PHP driver release should point to a tagged submodule
237
- version).
238
-
239
231
#### Update sources in build configurations
240
232
241
233
The Autotools and Windows build configurations (` config.m4 ` and ` config.w32 ` ,
@@ -261,11 +253,11 @@ libmongoc and libbson.
261
253
For example, the following lines might be updated for libmongoc:
262
254
263
255
```
264
- if $PKG_CONFIG libmongoc-1.0 --atleast-version 1.20 .0; then
256
+ if $PKG_CONFIG mongoc2 --atleast-version 2.1 .0; then
265
257
266
258
...
267
259
268
- AC_MSG_ERROR(system libmongoc must be upgraded to version >= 1.20 .0)
260
+ AC_MSG_ERROR(system libmongoc must be upgraded to version >= 2.1 .0)
269
261
```
270
262
271
263
#### Update tested versions in Evergreen configuration (libmongoc only)
@@ -277,7 +269,7 @@ information about the build tasks and where they are used. In general, we test
277
269
against two additional versions of libmongoc:
278
270
279
271
- The upcoming patch release of the current libmongoc minor version (e.g. the
280
- ` r1 .x` branch)
272
+ ` r2 .x` branch)
281
273
- The upcoming minor release of libmongoc (e.g. the ` master ` branch)
282
274
283
275
#### Update sources in PECL package generation script
@@ -307,5 +299,6 @@ test suite passes. Once done, commit the changes to all of the above
307
299
files/paths. For example:
308
300
309
301
``` shell
310
- git commit -m " Bump libmongoc to 1.20.0" config.m4 config.w32 src/libmongoc src/LIBMONGOC_VERSION_CURRENT sbom.json
302
+ git commit -m " Bump libmongoc to 2.1.0" config.m4 config.w32 src/libmongoc sbom.
303
+ json
311
304
```
0 commit comments