Dear Wiki user, You have subscribed to a wiki page or wiki category on "Thrift Wiki" for change notification.
The "HowToRelease" page has been changed by BryanDuxbury. http://wiki.apache.org/thrift/HowToRelease -------------------------------------------------- New page: 1. If this is the first release in a given major or minor version, (ie, 0.4 or 1.0): 1. Branch TRUNK to branches/N.x where N is the version you are attempting to release. For instance, 0.4.x or 1.2.x. 1. Check out the new branch locally. 1. Update configure.ac's [thrift] variable to the version you are releasing and commit this change. 1. Generate the contents of the CHANGES file. 1. (There may be other version numbers you want to update, like the Ruby gem version.) 1. Run ./bootstrap.sh && ./configure 1. Run "make dist". This should produce thrift-[version].tar.gz in the root of your project. 1. Change the name of thrift-[version].tar.gz to thrift-[version]-rc[release candidate num].tar.gz. The release candidate numbers should start at zero. 1. Sign the tarball: gpg -ba [tarball.tar.gz] > [tarball.tar.gz].asc 1. Compute the sha1 and md5 hashes of the tarball: sha1 [tarball.tar.gz] > [tarball.tar.gz].sha1 && md5 [tarball.tar.gz] > [tarball.tar.gz].md5 1. Copy the tarball, signature, and hashes to somewhere public. I used people.apache.org:~/public_html, but you may use any publicly-accessible hosting. 1. Write an email to thrift-dev with the following information: 1. The SVN branch that contains the code you're releasing 1. The link to download the tarball and signature 1. The md5 and or sha1 hashes 1. Language formally proposing that the tarball be accepted as the release at such-and-such version 1. After the vote has been open for 72 hours, check if it has passed. 1. If the vote has passed, write an email like the one described above to gene...@incubator with the same information, but also that the vote has passed in the main Thrift project. 1. After this vote has been open for 72 hours, check if it has passed. 1. If the vote has passed, congratulations, you have a valid release. And then... (work in progress) 1. Copy the tarball, signature, and hashes to the official artifact repo 1. Update the website to point to the new version 1. "Release" the version you released in JIRA
