Skip to content

[Task] Absorb selected MUIO v5.6 changes on origin/main #457

@SeaCelo

Description

@SeaCelo

Upstream MUIO has moved past v5.5. Four "MUIO ver 5.6" commits landed in early April, and one more on May 5 reworked the new "indicators" feature. I'm treating that May 5 commit as part of the v5.6 set since it changes the same code.

I checked what it would take to bring this in by simulating the merge from where MUIOGO is today.

This issue is the tracker for that work.

The rule is the same as the v5.5 sync (#388, #393): follow upstream by default, and only deviate where MUIOGO has to keep something working that upstream doesn't care about — portability, security, our setup flow, that kind of thing.

A few things worth knowing up front:

The work is split into five sub-issues, sub-PRs target a long-lived feature/v56-ui-sync branch (already pushed), and the final merge from feature/v56-ui-sync to main is the last step (mirrors #422).

Sub-issues:

Order: #458 first; #459, #460, #461 can run in parallel after; #462 lands last.

Done when:

  • the five sub-issues are closed
  • the final PR from feature/v56-ui-syncmain is merged
  • ./scripts/setup.sh --check and ./scripts/smoke.sh pass
  • demo case solves end-to-end with GLPK and CBC
  • a user can add an indicator to a case, save, reload, and still see it
  • Versions.html and WebAPP/index.html reflect "MUIO 5.6"

Related:

Metadata

Metadata

Assignees

Type

No fields configured for Task.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions