stdcxx-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Stdcxx Wiki] Update of "PublishingReleases" by MartinSebor
Date Thu, 01 May 2008 16:52:42 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Stdcxx Wiki" for change notification.

The following page has been changed by MartinSebor:

The comment on the change is:
Documented process for creating and publishing stdcxx releases.

New page:
This page describes the process of creating and publishing a release of Apache C++ Standard

 1. Create a Release Candidate [RC].
  1. Check out the latest {{{-rc-}}} tag corresponding to the release into a local copy and
remove all {{{.svn}}} directories from the local copy.
     Example: {{{
     $    svn co  $HOME/stdcxx-4.2.1/
       && find $HOME/stdcxx-4.2.1/ -name .svn -type d | xargs rm -rf }}}
  1. Create a tarball of the local copy named {{{stdcxx-X.Y.Z.tar.gz}}} with {{{X.Y.X}}} corresponding
to the version to be released, an MD5 sum file of the tarball with the same name as the tarball
and the {{{.md5}}} extension, and a PGP signature file for the tarball with a {{{.asc}}} extension.
See [ Signing Releases] for details.
     Example: {{{
     $    tar -cf stdcxx-4.2.1.tar stdcxx-4.2.1 \
       && gzip stdcxx-4.2.1.tar && md5sum stdcxx-4.2.1.tar.gz \
       && gpg --armor --output stdcxx-4.2.1.tar.gz.asc --detach-sig stdcxx-4.2.1.tar.gz}}}
 1. Copy the tarball and all its artifacts to a publicly accessible location such as {{{$HOME/public_html/}}}
visible on the web.
 1. Start a vote on the RC on, optionally CC'ing,
allowing at least 72 hours before closing. The subject of the post should start with the string
[VOTE] followed by the version to be released. In the body of the post include links to the
tarball and all the relevant artifacts. See for example: [
[VOTE] stdcxx-4.2.1 release].
 1. Once the vote passes with at least three +1 binding votes and no vetos after 72 hours
or more and has been closed, copy the release candidate and all necessary artifacts to [
/www/] and, if necessary, update the [
KEYS] file with the public key used to sign the release.

View raw message