Professional Documents
Culture Documents
Release Procedure
Release Procedure
============================================
- update `docs/THANKS`
- make sure all relevant changes are committed on the master branch
- tag the git repo in this style: `git tag -a curl-7_34_0`. -a annotates the
tag and we use underscores instead of dots in the version number.
- tag the repo with the same tag as used for the source repo
- make sure all relevant changes are committed and pushed on the master branch
on github
---------
- edit the newly made release tag so that it is listed as the latest release
inform
------
celebrate
---------
Basics
------
- During the first 4 weeks after a release, we allow new features and changes
to curl and libcurl. If we accept any such changes, we bump the minor number
used for the next release.
- During the second 4-week period we do not merge any features or changes, we
then only focus on fixing bugs and polishing things to make a solid coming
release.
Coming dates
------------
Based on the description above, here are some planned release dates (at the
time of this writing):