Difference between revisions of "CDash:Tagging"

From KitwarePublic
Jump to: navigation, search
Line 1: Line 1:
To release a new CDash (let's say revision 1.2) please follow the current steps:
+
To release a new CDash (let's say revision 1.2) please follow these steps:
  
# Tag/Branch the current trunk repository with Release-1-2-0 (this is the main release)
+
* Update the version in package.json and include/version.php to 1.2.0
# Update the version in the file cdash/version.php to 1.2.0
+
* Add the following lines to js/cdashUpgrade.js and s:
# Tag/Branch the current trunk repository with Release-1-2 (this is the branch release)
+
# Update the version in the file cdash/version.php to 1.2.1
+
# Update the version in the trunk cdash/version.php to 1.3.0
+
# In the trunk change the file javascript/cdashUpgrade.js and add the following lines:
+
  
 
   else if(version < 1.4)
 
   else if(version < 1.4)
Line 12: Line 8:
 
     nextstep = upgrade_1_4;
 
     nextstep = upgrade_1_4;
 
     }
 
     }
 
and
 
  
 
   function upgrade_1_4()
 
   function upgrade_1_4()
Line 22: Line 16:
 
     }
 
     }
  
# In upgrade.xsl add:
+
* In upgrade.xsl add:
 
   <nowiki><div id="Upgrade-1-4-Status"></div></nowiki>
 
   <nowiki><div id="Upgrade-1-4-Status"></div></nowiki>
  
# In upgrade.php add:
+
* In upgrade.php add:
  
 
   <nowiki>// 1.4 Upgrade
 
   <nowiki>// 1.4 Upgrade
Line 37: Line 31:
 
     return;
 
     return;
 
     }</nowiki>
 
     }</nowiki>
 +
 +
* Make a commit from these changes with the message "CDash 1.2.0".
 +
* Change the version in package.json and version.php to 1.3.0
 +
* Commit this change as "CDash 1.3.0 (development version)"
 +
* After these commits have been merged to master, tag the "CDash 1.2.0" commit as "v1.2.0" and push the tag upstream.
  
 
* Upgrade the change log:
 
* Upgrade the change log:
 
   
 
   
 
   http://public.kitware.com/Wiki/CDash:Upgrade#Change_logs
 
   http://public.kitware.com/Wiki/CDash:Upgrade#Change_logs
 
* Create new version in Mantis:
 
 
  http://www.cdash.org/Bug
 

Revision as of 09:54, 28 December 2016

To release a new CDash (let's say revision 1.2) please follow these steps:

  • Update the version in package.json and include/version.php to 1.2.0
  • Add the following lines to js/cdashUpgrade.js and s:
 else if(version < 1.4)
   {
   nextstep = upgrade_1_4;
   }
 function upgrade_1_4()
   {
   var text = "Applying 1.4 patches";
   $("#Upgrade-1-4-Status").html("<img src=\"images/loading.gif\"/> "+text+"...");
   sendAjax("#Upgrade-1-4-Status","upgrade.php?upgrade-1-4=1",text,done);  
   }
  • In upgrade.xsl add:
 <div id="Upgrade-1-4-Status"></div>
  • In upgrade.php add:
 // 1.4 Upgrade
  if(isset($_GET['upgrade-1-4']))
    {  
    // Set the database version
    setVersion();

    // Put that the upgrade is done in the log
    add_log("Upgrade done.","upgrade-1-4");
    return;
    }
  • Make a commit from these changes with the message "CDash 1.2.0".
  • Change the version in package.json and version.php to 1.3.0
  • Commit this change as "CDash 1.3.0 (development version)"
  • After these commits have been merged to master, tag the "CDash 1.2.0" commit as "v1.2.0" and push the tag upstream.
  • Upgrade the change log:
 http://public.kitware.com/Wiki/CDash:Upgrade#Change_logs