To update a mature branch for release.
Select patches based upon developer input. Have the developer
provide before and after file revision info so you can do
cvs upd -jbefore -jafter file
for each file in the patch. Where needed, work with developer
to back port patch.
Update CHANGES as you integrate patches.
When ready for release, update version and CHANGES to reflect new release.
For the CHANGES file, add the date of the release, and drop Engineering bit
for the release.
Update version.var, specifically: the ol_patch, ol_api_inc, and
ol_release_date values.
If the library API hasn't changed, bump ol_api_revision
If the library API has changed, bump ol_api_current and ol_api_age and reset
ol_api_revision to zero
Lay release tag. For example:
cvs tag OPENLDAP_REL_ENG_2_3_35
Update merge point, and finally notify the foundation.
That's basically it. It might be good to elaborate a bit more on precisely
how to update version.var (to get the shared library versioning correct) and
misc. other stuff.
I
quanah@openldap.org |