Milestone 8.1

Issue #11 resolved
David Dickinson created an issue

Version 8.1 - our first feature release with the git+Bitbucket workflow - has been a long time coming! Our original plan was for 8.1 to include some large changes to the memory layout and the field solve that would significantly improve performance and scalability. These are not quite ready, but we have accumulated many other features which are currently in next but not in master. We’ve decided to release 8.1 to make these features available, and to get them tested before making other significant changes.

The following unmerged PRs are scheduled for the 8.1 release:

As ever, this list is provisional and evolving, so please feel free to comment or suggest other feature for inclusion!

Key:

✅ merged into next

🕐 will be included, but not yet merged

❓ may be included, perhaps require more work/refactoring

➡ delayed until later release

Comments (43)

  1. Joseph Parker

    Version 8.1 - our first feature release with the git+Bitbucket workflow - has been a long time coming! Our original plan was for 8.1 to include some large changes to the memory layout and the field solve that would significantly improve performance and scalability. These are not quite ready, but we have accumulated many other features which are currently in next but not in master. We’ve decided to release 8.1 to make these features available, and to get them tested before making other significant changes.

    The following unmerged PRs are scheduled for the 8.1 release:

    PRs marked ??? may require more work/refactoring.

    As ever, this list is provisional and evolving, so please feel free to comment or suggest other feature for inclusion!

  2. David Dickinson reporter

    We should probably also finish migrating the namelist documentation from the old wiki to the source code for this release.

  3. David Dickinson reporter

    @Joseph Parker are you able to move your comment into the issue description? Currently we’re not able to edit the comment so I can’t mark a few of these as done (Change the default of bouncefuzz to address issue #116, Feature/improve response matrix dumping issue 96, Ignore absence of explicit source terms in restart files and Add include_explicit_source_in_restart input flag are in next now).

  4. David Dickinson reporter

    I’d propose delaying the memory profiling. There’s been some discussion about adopting a different approach which may make subsequent changes easier but would require preprocessing all files. Probably worth resolving that before we put the code in.

  5. Log in to comment