Skip to content
glynos edited this page Apr 22, 2012 · 4 revisions

When committing to a release we want to do the following:

Check that everything compiles and that the unit tests succeed

Build cpp-netlib from scratch and run the tests locally. Secondly, refer to the CI server (http://173.255.250.89:8080/) to confirm that cpp-netlib builds and the test run succeeds on any other platforms we want to support.

Tag the commit

$bash> cd $CPP_NETLIB_ROOT
$bash> git tag -a 0.9.4 -m "Version 0.9.4"
$bash> git push origin --tags

Update the documentation

Particularly the whats_new.rst file, and the version numbers in index.rst and conf.py and check that any new features have been added to the docs.

Build the documentation.

On Linux, I do this:

$bash> cd $CPP_NETLIB_ROOT/libs/network/doc
$bash> make html

Copy the documentation to git://github.com/cpp-netlib/cpp-netlib.github.com.git

On Linux, I do something this:

$bash> cd $CPP_NETLIB_DOC_ROOT
$bash> cp -R $CPP_NETLIB_ROOT/libs/network/doc/_build/html latest
$bash> cp -R $CPP_NETLIB_ROOT/libs/network/doc/_build/html 0.9.4
$bash> git add 0.9.4
$bash> git commit -a -m "Updated documentation."
$bash> git push origin master

Where 0.9.4 is the latest version number.

To do

Automate this process, especially the documentation generation.

Clone this wiki locally
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy