Difference between revisions of "Release Details"

From Einstein Toolkit Documentation
Jump to: navigation, search
Line 3: Line 3:
 
<h2>Schedule for ET_2014_11</h2>
 
<h2>Schedule for ET_2014_11</h2>
 
<ul>
 
<ul>
  <li>2014-11-03:
+
  <li>2015-04-27:
 
     Slight freeze: no new major additions to the toolkit (new thorns or tools, major patches)</li>
 
     Slight freeze: no new major additions to the toolkit (new thorns or tools, major patches)</li>
  <li>2014-11-10:
+
  <li>2015-05-30:
 
     Feature freeze: no new features allowed anymore, extensive testing begins</li>
 
     Feature freeze: no new features allowed anymore, extensive testing begins</li>
  <li>2014-11-11:
+
  <li>2015-05-04:
 
     Release branches are created, development version un-frozen again</li>
 
     Release branches are created, development version un-frozen again</li>
  <li>2014-11-11:
+
  <li>2015-05-08:
 
     Total freeze of release branches, preparation of tar-balls etc. begins</li>
 
     Total freeze of release branches, preparation of tar-balls etc. begins</li>
  <li>2014-11-12:
+
  <li>2015-05-11:
 
     Target release date (or earlier if "ready")</li>
 
     Target release date (or earlier if "ready")</li>
 
</ul>
 
</ul>
Line 17: Line 17:
 
<h2>Tools/Links</h2>
 
<h2>Tools/Links</h2>
 
<ul>
 
<ul>
  <li>The release branch name will be ET_2014_05</li>
+
  <li>The release branch name will be ET_2015_05</li>
 
  <li>The release name is not yet fixed</li>
 
  <li>The release name is not yet fixed</li>
 
  <li>The list of proposed names for last release was
 
  <li>The list of proposed names for last release was
Line 36: Line 36:
 
   </ul>
 
   </ul>
 
  </li>
 
  </li>
  <li>[http://einsteintoolkit.org/release-info/parse_testsuite_results.php Testsuite Status page]
+
<li>[https://build.barrywardell.net/view/EinsteinToolkitMulti/job/EinsteinToolkitReport-sandbox/ New Testsuite status page]</li>
 +
  <li>[http://einsteintoolkit.org/release-info/parse_testsuite_results.php Old 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
 
       have them automatically included)</li>
 
       have them automatically included)</li>
Line 42: Line 43:
 
  <li>Release announcements: [[Release Announcement|short]] and [[Detailed Release Announcement|long]]</li>
 
  <li>Release announcements: [[Release Announcement|short]] and [[Detailed Release Announcement|long]]</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>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://www.cct.lsu.edu/~knarf/ET_2012_11/log.xml Einstein Toolkit ChangeLog]</li>
 
<li>[[ChangeLog_ET_2013_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) I usually (at irregular intevals) test the testsuites on Debian (stable), Ubuntu (latest) and Fedora (latest though that requires changes to simfactory I think) machines. This tests debian.cfg, ubuntu.cfg and fedora.cfg so that they work with the [[Simplified_Tutorial_for_New_Users|simplified instructions]]. I do not test on OSX (since I hardly use it). (Roland)</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) I usually (at irregular intevals) test the testsuites on Debian (stable), Ubuntu (latest) and Fedora (latest though that requires changes to simfactory I think) machines. This tests debian.cfg, ubuntu.cfg and fedora.cfg so that they work with the [[Simplified_Tutorial_for_New_Users|simplified instructions]]. I do not test on OSX (since I hardly use it). (Roland)</li>
 
</ul>
 
</ul>

Revision as of 08:25, 4 May 2015

Schedule for ET_2014_11

  • 2015-04-27: Slight freeze: no new major additions to the toolkit (new thorns or tools, major patches)
  • 2015-05-30: Feature freeze: no new features allowed anymore, extensive testing begins
  • 2015-05-04: Release branches are created, development version un-frozen again
  • 2015-05-08: Total freeze of release branches, preparation of tar-balls etc. begins
  • 2015-05-11: Target release date (or earlier if "ready")

Tools/Links

  • The release branch name will be ET_2015_05
  • The release name is not yet fixed
  • The list of proposed names for last release was
    • Mary Somerville
    • Caroline Herschel
    • Chien-Shiung Wu
    • Cecilia Payne-Gaposchkin
    • Lorentz
    • Tesla
    • Wheeler
    • DeWitt
    • Feynman
    • Hilbert
    • Turing
    • Brahe
    • Planck
  • New Testsuite status page
  • Old Testsuite Status page (add the testsuite *.log files created by scripts below to the repository at [1] to have them automatically included)
  • Instructions for running the tests using SimFactory: 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/
  • 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) I usually (at irregular intevals) test the testsuites on Debian (stable), Ubuntu (latest) and Fedora (latest though that requires changes to simfactory I think) machines. This tests debian.cfg, ubuntu.cfg and fedora.cfg so that they work with the simplified instructions. I do not test on OSX (since I hardly use it). (Roland)

Release Plan

TaskDue dateResponsibleStatus
Regenerate all Kranc thorns (McLachlan, EinsteinExact and WeylScal4)
Test all examples in the gallery (http://einsteintoolkit.org/about/gallery/) with the current thornlist, and update the thornlist mentioned on the page
(Re)run Testsuitesdatura as necessary ?
bluewaters as necessaryRoland

balsara4_2d passes, test_simpson has convergence order 4.0+/-1e-3, SphericalHarmonicRecon/regression_test has an unexpected non-zero value in the middle of a region with lots of zeros, looks like bug of some sort the remaining tests are likely looking at data too close to singularities all tests pass if I compile with -O3 -mno-fma -mno-fma4 instead of -Ofast

forge as necessary ?
hopper as necessary good
jenkins as necessary ?
lonestar as necessary
orca as necessary good
pandora as necessary ?
philip as necessary ?
queenbee as necessary updated 20121101
stampede as necessary ?
stampede-mic as necessary cannot run testsuite (file system is unreliable)
supermikeas necessary ?
tezpur as necessary updated 20121101
trestles as necessary updated 20121026
supermuc as necessary ?
vesta as necessary cannot run testsuite (job submission is weird)
zwicky as necessary
(private) amarok as necessaryPeter updated 20121101
(private) bethe as necessaryRoland
(private) cygnus as necessaryMatt ?
(private) newhorizonsas necessaryYosef?
(private) redshift as necessaryErik good
(private) spine as necessaryFrank ?
(private) titan as necessaryErik good
(private) topf as necessaryFrank √?
Fix Testsuites some thorn someone
Check & Improve Documentation (www, wiki)everyone
Write announcement texts (short and long)Frank
Create release branchsvn.einsteintoolkit.org Frank?
svn.cactuscode.org Frank?
carpetcode.org Frank?
aei.mpg.de Frank?
svn.cct.lsu.edu Frank?
github.com/ianhinder/Kranc.gitFrank?
github.com:gridaphobe/CRL.git Frank?
github.com:rhaas80/Outflow.git Frank?