Difference between revisions of "Release Details"

From Einstein Toolkit Documentation
Jump to: navigation, search
Line 7: Line 7:
 
* Roland Haas, release manager emeritus
 
* Roland Haas, release manager emeritus
  
<h3>Possible Functionality</h3>
+
<h3>Proposed Inclusions</h3>
* FLRW solver [https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolver-in-et ticket]
+
** Fishbone-Moncrief gallery example [https://bitbucket.org/einsteintoolkit/tickets/issues/2687/add-fishbone-moncrief-disk-gallery-example Ticket #2687] -- needs reviewer
* FUKA v2 (maybe, see [http://lists.einsteintoolkit.org/pipermail/users/2022-June/008586.html announcement])
+
** Elliptica reader (and solver timeline) [https://bitbucket.org/einsteintoolkit/tickets/issues/2619/include-ellipitca-reader-in-einstein Ticket #2619] -- Beyhan as possible reviewers
* [[CarpetX_Transition|CarpetX prerelease]]
+
** FUKA reader [http://lists.einsteintoolkit.org/pipermail/users/2022-June/008586.html announcement] and [https://bitbucket.org/einsteintoolkit/tickets/issues/2692/inclusion-of-fuka-importer-thorns Ticket #2692]
* IllinoisGRMHD major update and feature enhancement (tab EOS + neutrino leakage)
+
** IllinoisGRMHD major update and feature enhancement [https://bitbucket.org/einsteintoolkit/tickets/issues/2690/include-new-illinoisgrmhd-with-tabulated Ticket #2690]
 +
** NRPyEOS [https://bitbucket.org/einsteintoolkit/tickets/issues/2688/include-nrpyeos-in-next-et-release Ticket #2688]
 +
** NRPyLeakage [https://bitbucket.org/einsteintoolkit/tickets/issues/2689/include-nrpyleakage-in-next-et-release Ticket #2689]
 +
** Minor feature improvement to particle_tracerET [https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-particle_traceret Ticket #2691]
 +
** TwoPunctures_BBHSF and NPScalars_SF in Canuda/Scalar for binary black holes + scalar fields [https://bitbucket.org/einsteintoolkit/tickets/issues/2697/include-bbh-scalar-field-initial-data-code Ticket #2697]
 +
** New kuibit version [https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-140 Ticket #2696]
 +
 
 +
* [[CarpetX Transition|CarpetX pre-release]] code review also beginning during this release cycle
  
 
<h3>Schedule</h3>
 
<h3>Schedule</h3>

Revision as of 23:08, 2 February 2023

Details for ET_2023_05

Release team

  • Leo Werneck, release manager
  • Sam Cupp, release co-manager
  • Roland Haas, release manager emeritus

Proposed Inclusions

Schedule

  • 2023-01-18 (-18wk): propose functionality to include
  • 2023-02-01 (-16wk): choose features which are going to be included
    • ask for review volunteers, assign tasks to people
    • create tickets for each proposed item tickets repo
    • decide on a list of release-critical compute systems
  • 2023-03-15 (-10wk): all codes proposed for inclusion in master branch (still under review)
  • 2023-03-29 (-8wk): all codes proposed for inclusion have finished review
  • 2023-03-29 (-8wk): regenerate Kranc and NRPy+ codes
  • 2023-03-29 (-8wk): start testing
    • gallery examples
    • test simfactory on clusters
    • test in docker images / VM for "common" OS
  • 2023-04-19 (-5wk): decide on name
  • 2023-04-26 (-4wk): feature freeze: no new features allowed anymore, extensive testing begins
  • 2023-04-26 (-4wk): create first draft of the release notes as an md file
    • Identify contributors to the release
    • Identify the release team
    • Identify major changes to call out in the release notes.
  • 2023-04-26 (-4wk): announce date publicly
  • 2023-05-10 (-2wk): draft release announcement
  • 2023-05-17 (-1wk): testing done
  • 2023-05-17 (-1wk): hard freeze, no more changes at all
  • 2023-05-17 (-1wk): make branches, prepare updates for websites, test-send announcement (to maintainers@einsteintoolkit.org)
  • 2023-05-24: release date

Details for ET_2022_11

Possible Functionality

Schedule

  • 2022-07-14 (4mo, 2weeks): propose functionality to include
  • 2022-07-21 (4mo): Choose features which are going to be included
    • ask for review volunteers, assign tasks to people
    • create tickets for each proposed item tickets repo
    • decide on a list of release-critical compute systems
  • 2022-09-01 (-10wk): all codes proposed for inclusion in master branch (still under review)
  • 2022-09-15 (-2mo): all codes proposed for inclusion have finished review
  • 2022-09-15 (-2mo): Regenerate Kranc and NRPy+ codes
  • 2022-09-15 (-2mo): start testing
    • gallery examples
    • test simfactory on clusters
    • test in docker images / VM for "common" OS
  • 2022-10-06 (-5wks): decide on name
  • 2022-10-13 (-1mo): Feature freeze: no new features allowed anymore, extensive testing begins
  • 2022-10-13 (-1mo): Create first draft of the release notes as an md file
    • Identify contributors to the release
    • Identify the release team
    • Identify major changes to call out in the release notes.
  • 2022-10-13 (-1mo): Announce date publicly
  • 2022-10-27 (-2wk): draft release announcement
  • 2022-11-03 (-1wk): testing done
  • 2022-11-03 (-1wk): hard freeze, no more changes at all
  • 2022-11-03 (-1wk): make branches, prepare updates for websites, test-send announcement (to maintainers@einsteintoolkit.org)
  • 2022-11-10: release, Thu before SC 22 and 2 wks before US Thanksgiving

(1mo = 4wks)

Release names

Tools/Links

  • Testsuite status page
  • Instructions for running the tests using SimFactory: Testsuite Machines
  • Release announcements: wiki sandbox
  • See list in Release Process
  • Testing is performed on the latest version of common operating systems, for example Debian, Ubuntu, Fedora, Scientific Linux, Mac OS etc. People often want to build the ET on their laptop or workstation. Instructions for which packages etc are needed can be found in the respective Simfactory option list. This information could also be provided on the Cactus website.

Release Plan

Test status is on Release coordination page.