DevNotes_29May2026_Technical

Next Refactor Hackathon

• Refactor Hackathon II: June 3-5
• Wiki Page
• Bad Dates for future Hackathons:
  • NOBUGS: Sept. 21-25
  • Contributor Camp: Nov. 3-9
  • ESS-ILL User Meeting: Nov. 18-20
• Work Pacakges:
  • SasView:
    • Undo stack planning and design (http://github.com/orgs/SasView/discussions/2951) - Piotr Rozycko
    • Data Explorer data/plot/trend/perspective representations
    • Plotting refactor integration - https://github.com/SasView/sasview/tree/refactor_24_plotting_refactor_integration_rebase
    • HDF file loader interface (general loader for any HDF file) - Paul Butler
    • ASCII file loader interface (fix and/or document issues found in testing) - Paul Butler - 2D DAT files still in question - https://github.com/SasView/sasview/issues/3533
    • MuMag data handling - The base work is in https://github.com/SasView/sasview/tree/refactor24-data-explorer
    • Slicer front-end
  • SasData:
    • Data loaders (ensure all are working and add as-needed)
    • Data Trends (finalize) - Miguel Gonzalez
    • Slicing backend - Jeff Krzywon
    • SasData refactor API: https://github.com/SasView/sasdata/tree/sasview-database - Jeff to finalize
  • SasModels:
    • SasData integration (remove built-in data objects)

Pull Requests to Discuss

• SasView
• SasModels
• SasData

6.2.0

• Code freeze: Alpha 2 is out. Alpha 3 pending
• Outstanding PRs and Issues:
• Related to an ADR discussion, but what can come after the code freeze?
  • Gray area
    • Bug fixes for features not introduced in v6.2.0
    • Models in sasmodels
    • Documentation. Just for new features or for all documentation?
  • Within reason
    • Bug fixes for features added between v6.1.3 and v6.2.0
  • Always a yes
    • Release notes
    • Build/CI issues

Status updates of ongoing projects

• CodeScene and Ruff (Paul S./Jeff)
  • CodeScene integration - Minimal Safety Net complete
    • Enabling on sasdata - Wait until after 6.2.0 release

ADRs

• To finalize:
  • https://github.com/orgs/SasView/discussions/3171#discussioncomment-15497631: 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
• 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
    • Convert https://github.com/SasView/sasview/wiki/contribution_acknowledgments to an ADR

AOB?