AGEPRO-GUI/CoreLib Versioning with AGEPRO Calculation Engine

[efletcherPIFSC]

Next updates for AGEPRO-GUI/CoreLib will contain

• AuxiliaryOutputFlag(SummaryStockFlag) GUI update. (Update GUI interface for auxilliaryOutputFlag(summaryStockFlag) options #19; AGEPRO: auxillaryOutputFlag(stockSummaryFlag) Changes AGEPRO#13)
• Bugfixes
  • "SET" button does not work after "Create New Case" #17
  • Invalid Agepro Model (Parametric Curve-Striped Marlin) questions #18

Changes to AuxiliaryOutputFlag(SummaryStockFlag) will update the AGEPRO Input File format to AGEPRO VERSION 4.25 (PIFSCstockassessments/AGEPRO#11), which will be rolled in a future AGEPRO Calculation Engine release.

GUI/Calculation Engine Version Disparity

The 4.3.X GUI version is a "revamp" from the NOAA Fisheries Toolbox GUI based 4.2.X AGEPRO GUI, but uses version 4.2 of the AGEPRO Calculation Engine

As of December 2024, the current version of AGEPRO-GUI is version 4.3.5, which uses AGEPRO VERSION 4.0 input data files. AGEPRO-GUI releases is listed on PIFSCstockassessments GitHub and NOAA Fisheries Integrated Toolbox. AGEPRO's NOAA FIT page is tagged with the AGEPRO-GUI version v4.3.5

https://github.com/PIFSCstockassessments/AGEPRO-GUI/releases
https://noaa-fisheries-integrated-toolbox.github.io/AGEPRO

Solutions

To fix the version disparity (and confusion) between GUI and calculation engine versions, I believe that next version release should emphasize AGEPRO Calculation Engine Version but also maintain a its own version number.

The following are what the AGEPRO-GUI versioning scheme will be:

• <CalcVer>-<GUIver> : 4.25-4.3.6
  • This keeps the AGEPRO-GUI versioning scheme, but the combining the CalcVer and GUIver strings into one makes it comfusing to read
• <CalcVer>-gui<GUI_Release> and <CalcVer>-glib<CoreLib_Release>: 4.25-gui6 4.25-glib6
  • Its to the point ("It is the gui ver of Calc"), but introduces a new versioning scheme for GUI releases. If "4.3.6" was the next GUI release, then it would numbered as 4.25-gui6. CoreLib can be labeled similarly, but to should be numbered as the same as the GUI release (in this example, 4.25-glib6).

[efletcherPIFSC]

After some thought, keeping AGEPRO-GUI current sematic versioning format is sufficient.