DevNotes_17Apr2026_Technical

Next Refactor Hackathons

• Refactor Hackathon I: Mar 16-17
• Refactor Hackathon II: ~June
• Refactor Hackathon III: ~September
• Refactor Hackathon IV: ~December
• Bad Dates:
  • Vacation Week: June 22-26
  • ACNS: July 12-16
  • NCNR Summer School: July 27-31
  • NOBUGS: Sept. 21-25
  • Contributor Camp: Nov. 3-9
  • ESS-ILL User Meeting: Nov. 18-20
• Jeff to send Doodle Poll for Hackathon II working around bad dates list

Pull Requests

• SasView (17 open, 10 in draft, 1 approved)
  • Discuss:
    • Use browser for help: https://github.com/SasView/sasview/pull/3923
    • Release automation: https://github.com/SasView/sasview/pull/3918 - one release automation script that only lives in sasview, or separate scripts for each repo?
• SasModels (13 open, 5 in draft, 1 approved)
• SasData (10 open, 6 in draft)
  • SasData API: https://github.com/SasView/sasdata/pull/106 - Jeff to get into a mergeable state...

6.2.0

• Proposed code freeze date: May 15, with Alpha1 release on May 18
• What outstanding PRs should be included? Discuss:
  • Remove QtWebEngine
  • Parameter sliders
  • New models
  • Windows binary signing action has changed
  • Code sign actions to be deprecated
  • Matplotlib backends not bundled
• What features should be highlighted in the what's new panel? Candidates include:
  • Multiple slicers on one plot
  • Symmetric slicers
  • Close project
  • SAXS fitting using PDB
  • Data Operation panel rework
• SasModels and SasData releases planned
• Repo rights should be up-to-date for Sujaya. Need to add Paul S.

Status updates of ongoing projects

• CodeScene and Ruff (Paul S./Jeff)
  • CodeScene integration - Wiki In Progress
    • Jeff has finished the write up for Minimal Safety Net and integration
    • What thresholds should we use for different things?: https://github.com/SasView/sasdata/blob/master/.codescene/code-health-rules.json
    • Enabling on sasdata
• Citing sasview
  • Sasview.org: https://github.com/SasView/sasview.github.io/pull/32 - merged
  • SasView: https://github.com/SasView/sasview/pull/3918
    • One release automation script for all repos or one per repo?
    • Extend to sasview.github.io?
  • SasModels: https://github.com/SasView/sasmodels/pull/709
  • SasData: https://github.com/SasView/sasdata/pull/200

ADRs

• To finalize:
  • https://github.com/orgs/SasView/discussions/3171#discussioncomment-15497631: Linter
• Ongoing discussion:
  • https://github.com/orgs/SasView/discussions/3511: Use web browser instead of built-in window - Assign writer or keep to a discussion?
• New to discuss
  • No link: Defining the release process and release manager - Jeff to create discussion
    • 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
  • https://github.com/orgs/SasView/discussions/3475: Release automation - Assign tasks, including final write-up - Jeff
    • Zenodo generation: build_tools/release_automation.py - Jeff already working on it, likely will never be part of the CI - 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
    • Upload binaries to releases: Already working for nightly build, need to port - Jeff (with Wojtek...?)

AOB?

• Wojtek to co-supervise student this summer (MCR-ALS time-resolved analysis): Candidates being selected - how to integrate with trends a major question, considering the other tools already in the works that will need it
• SASBDB Project: Pre-final meeting and discussion led to Guinier analysis integration. Already exists in linear fit window, but not in a way that works for the BioSAS community.