Difference between revisions of "Release Details"

From Einstein Toolkit Documentation
Jump to: navigation, search
Line 3: Line 3:
 
<h2>Tools/Links</h2>
 
<h2>Tools/Links</h2>
 
<ul>
 
<ul>
  <li>The release branch name will be ET_2012_05</li>
+
  <li>The release branch name will be ET_2012_11</li>
 
  <li>[http://einsteintoolkit.org/release-info/parse_testsuite_results.php Testsuite Status page]
 
  <li>[http://einsteintoolkit.org/release-info/parse_testsuite_results.php Testsuite Status page]
 
     (add the testsuite *.log files created by scripts below to the repository at [https://svn.einsteintoolkit.org/www/release-info/] to
 
     (add the testsuite *.log files created by scripts below to the repository at [https://svn.einsteintoolkit.org/www/release-info/] to
Line 12: Line 12:
 
  <li>Release announced to: users@einsteintoolkit.org, {news|users}@cactuscode.org, Jennifer Claudet <jennifer@cct.lsu.edu> for AllCCT, http://hyperspace.aei.mpg.de/, http://astro-sim.org/</li>
 
  <li>Release announced to: users@einsteintoolkit.org, {news|users}@cactuscode.org, Jennifer Claudet <jennifer@cct.lsu.edu> for AllCCT, http://hyperspace.aei.mpg.de/, http://astro-sim.org/</li>
 
  <li>TODO update: List of commits since the last release: [http://damiana2.aei.mpg.de/~ianhin/etchangelog/log.xml Einstein Toolkit ChangeLog]</li>
 
  <li>TODO update: List of commits since the last release: [http://damiana2.aei.mpg.de/~ianhin/etchangelog/log.xml Einstein Toolkit ChangeLog]</li>
  <li>[[ChangeLog_ET_2012_05 | ChangeLog]] text</li>
+
  <li>[[ChangeLog_ET_2012_11 | ChangeLog]] text</li>
 
  <li>I would like to suggest that testing is performed on the latest version of common operating systems, for example Ubuntu, Fedora, Scientific Linux, Mac OS etc.  People often want to build the ET on their laptop or workstation.  We should provide somewhere instructions for which packages etc are needed.  This information is probably already available in the minds of the current developers who use these systems already, and this should be written up more formally somewhere.  This information could also be provided on the Cactus website.  We could have simfactory configurations to go with this. (Ian)</li>
 
  <li>I would like to suggest that testing is performed on the latest version of common operating systems, for example Ubuntu, Fedora, Scientific Linux, Mac OS etc.  People often want to build the ET on their laptop or workstation.  We should provide somewhere instructions for which packages etc are needed.  This information is probably already available in the minds of the current developers who use these systems already, and this should be written up more formally somewhere.  This information could also be provided on the Cactus website.  We could have simfactory configurations to go with this. (Ian)</li>
 
</ul>
 
</ul>

Revision as of 01:22, 8 October 2012

Tools/Links

  • The release branch name will be ET_2012_11
  • Testsuite Status page (add the testsuite *.log files created by scripts below to the repository at [1] to have them automatically included)
  • Simfactory is able to run testsuites now. Please use it to run testsuites, also to test this capability.
  • Information on running the tests on different machines (some duplication with release-info page): Testsuite Machines
  • Release announcements: short and long
  • Release announced to: users@einsteintoolkit.org, {news|users}@cactuscode.org, Jennifer Claudet <jennifer@cct.lsu.edu> for AllCCT, http://hyperspace.aei.mpg.de/, http://astro-sim.org/
  • TODO update: List of commits since the last release: Einstein Toolkit ChangeLog
  • ChangeLog text
  • I would like to suggest that testing is performed on the latest version of common operating systems, for example Ubuntu, Fedora, Scientific Linux, Mac OS etc. People often want to build the ET on their laptop or workstation. We should provide somewhere instructions for which packages etc are needed. This information is probably already available in the minds of the current developers who use these systems already, and this should be written up more formally somewhere. This information could also be provided on the Cactus website. We could have simfactory configurations to go with this. (Ian)

Release Plan

TaskDue dateResponsibleStatus
(Re)run Testsuitesamarok as necessaryPeter some failures
datura as necessaryIan
forge as necessaryJian ?
hopper as necessaryFrank some failures
kraken as necessaryIan 3 failures
lonestar as necessaryFrank
orca as necessaryErik ?
pandora as necessaryPeter some failures - ask Peter when running there
philip as necessaryFrank
queenbee as necessaryPeter
ranger as necessaryTanja
surveyor as necessaryErik ?
tezpur as necessaryPeter
trestles as necessaryFrank down
zwicky as necessaryRoland
(private) bethe as necessaryRoland
(private) cygnus as necessaryTanja
(private) newhorizonsas necessaryYosef?
(private) numrel as necessaryFrank √ (gcc)
(private) redshift as necessaryErik some failures
(private) topf as necessaryFrank
Fix Testsuites some thorn someone
Check & Improve Documentation (www, wiki)May 25everyone
Write announcement texts (short and long)May 21Frank
Create release branchsvn.einsteintoolkit.org May 28Frank?
svn.cactuscode.org May 28Frank?
carpetcode.org May 28Ian ?
aei.mpg.de May 28Frank?
svn.cct.lsu.edu May 28Frank?
github.com/ianhinder/Kranc.gitMay 28Ian ?
github.com:gridaphobe/CRL.git May 28Frank?