DevNotes_10Jul2026_Technical

New Topics to Discuss

Version 6.2.0

• Beta 2 is out
• This beta addresses the critical issues with the "Freeze Datasets" button on plots (and freezing datasets more widely), and the Mac documentation issue.
  • Further feedback from Mac users will be appreciated.
• Outstanding Issues:
  • See the top-level issue
  • Do any of these need to be addressed before release?
• Any further issues/additions to the list?

Status updates of ongoing projects

• CodeScene and Ruff (Paul S./Jeff)
  • CodeScene integration - Minimal Safety Net complete
    • Now merged into SasData - feedback welcome.

ADRs

• To finalize - Paul Sharp sent both out to the developers list for review:
  • https://github.com/orgs/SasView/discussions/3171#discussioncomment-17148772: Linter - to be proposed at next biweekly meeting
  • https://github.com/orgs/SasView/discussions/3475: Release automation - To be proposed at next biweekly meeting
    • Final write-up: https://github.com/orgs/SasView/discussions/3475#discussioncomment-16757778
    • Zenodo generation: build_tools/release_automation.py - Piotr to look into Zenodo DOI generation that he knows of in other repos
    • Pypi publishing: Work started in sasdata. Finalize and port to sasview and sasmodels - Piotr to work on - https://github.com/SasView/sasdata/blob/master/.github/workflows/test.yml#L84
    • Upload binaries to releases: Already working for nightly build. Port in progress - Draft PR
  • Minor comments to address for linter ADR, nothing received for release automation.
• Ongoing discussions:
  • https://github.com/orgs/SasView/discussions/3934: Defining the release process and release manager
    • Some of the process is outlined in https://github.com/SasView/sasview/wiki/DevNotes_DevGuide_ReleaseChecklistTemplate
    • Release notes for Dev releases? Cumulative from previous stable release or from last dev release? Final release should have cumulative.
    • Delete/pare-down/hide dev releases after stable release? As long as we keep the tags and the binaries, the release notes can be pared down. More work for release manager if pared down. Likely keep as is to not create more work for ourselves.
  • No Link: Contributing to SasView: Define the process, i.e. what the requestor needs to provide, level of support from the existing community, and what that gets the contributor
    • https://github.com/SasView/sasview/wiki/contribution_acknowledgments to an ADR - Paul B. to convert prior to the Nov. Contributor Camp

AOB?