On 5/19/2013 2:47 PM, Daniel James wrote:
On 19 May 2013 19:17, Edward Diener
wrote: What is the normal procedure of moving from 'trunk' to 'release' ? Is it merely adding the files to the release branch or is there a better subversion technique ( I guess I should already know this ) ? Is the release branch 'https://svn.boost.org/svn/boost/branches/release' ?
Yes. I think the best thing to do is to checkout the release branch, and then copy your libraries directories:
cd libs svn cp ^/trunk/libs/tti tti cd ../boost svn cp ^/trunk/boost/tti tti
Commit that, and then for other merge the other individual changesets from the root using something like: 'svn merge -c1234 -c5678 ^/trunk' (using the correct revision numbers for the changesets). Or if you prefer you could manually copy over the changes over.
Done ! I haven't updated the release version with the generated HTML documentation yet. I think I should wait since I anticipate some documentation changes before the release. I still need to update the expected-failures-markup.xml on both the trunk and release with the TTI expected failures for vacpp on Aix.
Once I move to release do I assume that any coding changes are forbidden but that documentation changes are allowed ?
Fixes are allowed until the 27th. And then again, once the beta is out.
Great ! Thanks ! Edward Diener