Tag 0.1.0 against Nektar 5.3.0 to make way for a 0.2.0 release against 5.4

[jwscook]

• [x] merge NESO https://github.com/ExCALIBUR-NEPTUNE/NESO/pull/191
• [x] merge https://github.com/ExCALIBUR-NEPTUNE/NESO/pull/208
• [x] merge https://github.com/ExCALIBUR-NEPTUNE/NESO/pull/225
• [x] merge dev into main
• [x] tag new release of NP
• [x] update NESO NP git submodule
• [x] update NESO-Spack git submodule
• [x] whole load of testing
• [x] tag NESO as 0.1.0 against Nektar 5.2

... next tag NESO 0.2.0 will be against Nektar 5.x

[jwscook]

This requires a 0.3.1 NESO-Particles for NESO 0.1.0 Requires a PR into NESO-Spack to conditionally apply the patch to 5.3.0 when 5.3.0 is being used in the nektar package, and ensure NESO 0.1.0 requires Nektar 5.3.0

[will-saunders-ukaea]

Created v0.3.1 - https://github.com/ExCALIBUR-NEPTUNE/NESO-Particles/releases/tag/v0.3.1

[jwscook]

Waiting for using namespace std fix bundled with cmake changes to be released in NESO-Particles.

[jwscook]

When NESO #191, #208 and #225 are merged then NP dev can be merged to main and the NESO NP submodule can be updated. Finally NESO can be released.

[oparry-ukaea]

191 and #208 are merged.

[jwscook]

225 to be merged today (hopefully)

[jwscook]

@will-saunders-ukaea to do the NP items on the TODO list today

[will-saunders-ukaea]

@will-saunders-ukaea to do the NP items on the TODO list today

https://github.com/ExCALIBUR-NEPTUNE/NESO/pull/236

[jwscook]

Owen has run tests with gcc / hipsycl and Will has built on Archer2 and will check that the tests run.

[will-saunders-ukaea]

Will has built on Archer2 and will check that the tests run.

Done

[jwscook]

Great - in that case we can merge, tag, and release!

[oparry-ukaea]

Resolved by #236