Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
glynos edited this pageApr 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 thewhats_new.rst file, and the version numbers inindex.rst andconf.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 togit://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

[8]ページ先頭

©2009-2025 Movatter.jp