Teleconference 2021-02-17

From VTKM
Revision as of 16:39, 15 February 2021 by Kmorel (talk | contribs) (Created page with "Attendees: == ECP Updates == * Let's think about possible highlights ** App engagement ** Success with porting (e.g. run on Aurora) ** Engagement with other ST teams (e.g. u...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Attendees:

ECP Updates

  • Let's think about possible highlights
    • App engagement
    • Success with porting (e.g. run on Aurora)
    • Engagement with other ST teams (e.g. using Kokkos)
    • WDM
      • Submitted highlight on integration with EFFIS
      • Expect to submit another highlight when used in a big run
    • Possible highlight slide on particle advection with WarpX (Matt).

Porting Activities

ECP task updates

ECP/VTK-m Project Management

Roundtable

We need some redesign design workflow for branchy release process

  • When we create a VTK-m release, we have a branch for that release (at least until the subsequent release).
  • New feature development continues on the main branch
  • _Bug fixes_ happen off the release branch
    • Get merged to both the release branch and the master branch

Should think about releasing VTK-m 1.6, 2.0.

Matt working on WarpX highlight.

Rename master branch?

  • Need to wait for some changes to git before the transition (for some automated features of repo).
  • Can we for a time have a master that mirrors the new default?
    • Don't know, but seems possible. Will have to look into that.