@@ -136,7 +136,7 @@ reflect the new sources and/or package version.
136136```
137137$ cd src/libmongoc
138138$ git fetch
139- $ git checkout 1.15 .0
139+ $ git checkout 1.20 .0
140140```
141141
142142During development, it may be necessary to temporarily point the libmongoc
@@ -175,9 +175,10 @@ collectively enumerate all of the the sources within the libmongoc submodule to
175175include in a bundled build.
176176
177177These variables should each have a shell command in a preceding comment, which
178- should be run to regenerate that particular list of source files. In the event
179- that either libmongoc or libbson introduce a new source directory, that will
180- need to be manually added (follow prior art).
178+ should be run to regenerate that particular list of source files. Each command
179+ may be run manually or ` scripts/update-submodule-sources.php ` may be used to
180+ update all variables. In the event that either libmongoc or libbson introduce a
181+ new source directory, that will need to be manually added (follow prior art).
181182
182183#### Update package dependencies
183184
@@ -189,11 +190,11 @@ error message in the `pkg-config` blocks for both libmongoc and libbson.
189190For example, the following lines might be updated for libmongoc:
190191
191192```
192- if $PKG_CONFIG libmongoc-1.0 --atleast-version 1.15 .0; then
193+ if $PKG_CONFIG libmongoc-1.0 --atleast-version 1.20 .0; then
193194
194195...
195196
196- AC_MSG_ERROR(system libmongoc must be upgraded to version >= 1.15 .0)
197+ AC_MSG_ERROR(system libmongoc must be upgraded to version >= 1.20 .0)
197198```
198199
199200#### Update tested versions in Evergreen configuration
@@ -221,7 +222,7 @@ and by ensuring that the test suite passes. Once done, commit the changes to all
221222of the above files/paths. For example:
222223
223224```
224- $ git commit -m "Bump libmongoc to 1.15 .0" config.m4 config.w32 src/libmongoc src/LIBMONGOC_VERSION_CURRENT
225+ $ git commit -m "Bump libmongoc to 1.20 .0" config.m4 config.w32 src/libmongoc src/LIBMONGOC_VERSION_CURRENT
225226```
226227
227228### Updating libmongocrypt
@@ -231,12 +232,13 @@ To update libmongocrypt, the steps are similar to the above:
231232```
232233$ cd src/libmongocrypt
233234$ git fetch
234- $ git checkout 1.0.1
235+ $ git checkout 1.3.0
235236$ make libmongocrypt-version-current
236237```
237238
238- Package dependencies in ` config.m4 ` must also be updated, as do the sources in
239- the PECL generation script.
239+ Package dependencies in ` config.m4 ` must also be updated (either manually or
240+ with ` scripts/update-submodule-sources.php ` ), as do the sources in the PECL
241+ generation script.
240242
241243## Releasing
242244
0 commit comments