Changes between Version 8 and Version 9 of BuildClientProcedure


Ignore:
Timestamp:
Jul 31, 2007, 1:12:36 PM (17 years ago)
Author:
Nicolas
Comment:

Merged Rom's additions with my formatting changes again

Legend:

Unmodified
Added
Removed
Modified
  • BuildClientProcedure

    v8 v9  
     1{{{
     2#!comment
     3Rom, please don't overwrite my formatting changes when you add new content! --Nicolas
     4}}}
     5
    16= Client Build Procedure =
    27
     
    712If this is a major or minor version change to an even numbered minor revision you'll need to fork the tree.
    813
    9 {{{
    10 1. Right-click on the 'boinc' directory from trunk, and then select 'TortoiseSVN\Branch/Tag'
    11 2. Change the "To URL:" to 'http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>'
    12 }}}
    13 
    14 Where <major> is the major version number and <minor> is the minor version number.
    15 
    16 {{{
    17 3. Adjust version numbers in both the new branch and truck so that the new branch and trunk
     14 1. Right-click on the 'boinc' directory from trunk, and then select 'TortoiseSVN | Branch/Tag'
     15 2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>`, where `<major>` is the major version number and `<minor>` is the minor version number.
     16 3. Adjust version numbers in both the new branch and truck so that the new branch and trunk
    1817   reflect the current development efforts.
    19 }}}
    2018
    2119The branch should represent the new stable major and even minor version numbers. Trunk should represent the
    2220next major and odd minor version number.
    2321
    24 The files that need to be modified are configure.ac and version.h.
     22The files that need to be modified are `configure.ac` and `version.h`.
    2523
    2624Example: Branch 5.10.x and Trunk 5.11.0.
     
    3230Increment the revision number in the files dealing with version numbers.
    3331
    34 The files that need to be modified are configure.ac and version.h.
     32The files that need to be modified are `configure.ac` and version.h`.
    3533
    3634Commit all changes to SVN.
    3735
    38 {{{
    39 1. Right-click on the branch directory, and then select 'TortoiseSVN\Branch/Tag'
    40 2. Change the "To URL:" to 'http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>_<revision>'
    41 }}}
     36 1. Right-click on the branch directory, and then select 'TortoiseSVN\Branch/Tag'
     37 2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>_<revision>`
    4238
    4339Where <major> is the major version number, <minor> is the minor version number, and <revision> is the revision number.
     
    4945== Sanity Test New Binaries ==
    5046
    51 Run the BOINC manager and attach to the BOINC alpha test project, let run for 15 mins. Traverse
    52 all the tabs, verify the status fields as a result traverses the crunching process.
     47Run the BOINC manager and attach to the BOINC alpha test project, let run for 15 mins. Traverse all the tabs, verify the status fields as a result traverses the crunching process.
    5348
    5449== Code Sign Binaries ==
    5550
    56 The the SignCode.cmd file from the win_build directory. This batch file should be run from within a Visual
    57 Studio command shell. SignCode should contain a series of the following line:
     51The the `SignCode.cmd` file from the win_build directory. This batch file should be run from within a Visual Studio command shell. !SignCode should contain a series of the following line:
    5852
    5953{{{
    60 
    6154signtool sign /f "boinc.pfx" /p "<password>" /d "BOINC Client Software" /du "http://boinc.berkeley.edu"
    6255/t "http://timestamp.verisign.com/scripts/timstamp.dll" /sha1 "2F0BDC8DD84A56417C68B53B29DD12155760652D"
    6356.\Build\Win32\ReleaseSigned\boinc.dll
    64 
    6557}}}
    6658
    6759A call to signtool should be executed for each binary shipped in the setup package.
    6860
    69 Use [urlhttp://msdn2.microsoft.com/en-us/library/aa906332.aspx pvk2pfx] to convert the spc/pvk certificate pair into
    70 a pfx file.
     61Use [http://msdn2.microsoft.com/en-us/library/aa906332.aspx pvk2pfx] to convert the spc/pvk certificate pair into a pfx file.
    7162
    7263Replace '<password>' with the correct private key password used to create the private/public key pair.