DevNotes_01May2026_Technical

Next Refactor Hackathon

• Refactor Hackathon II: June
• Wiki Page
• Lessons Learned from Previous:
  • Suggest 3 days
  • Too few check-ins (1-2/day)
  • Planning meeting was useful for task assignments
• Bad Dates for future Hackathons:
  • NOBUGS: Sept. 21-25
  • Contributor Camp: Nov. 3-9
  • ESS-ILL User Meeting: Nov. 18-20
• Doodle Poll
• Jeff to finalize Doodle poll and send out to developers list

Pull Requests to Discuss

• SasView
  • v6.1.3 changes: https://github.com/SasView/sasview/pull/3895 - Paul S.
• SasModels
• SasData
  • Remove units.py: https://github.com/SasView/sasdata/pull/201 - Paul S. to remove unused imports and merge
  • SasData API: https://github.com/SasView/sasdata/pull/106 - Jeff to finalize during next hackathon, if not before

6.2.0

• Code freeze: May 15, with Alpha1 release on May 18
• What outstanding work should be included? Discuss:
  • Remove QtWebEngine
    • With this merged, will this allow a conda-forge release?
  • Parameter sliders
  • New models
• What other work should be added?
  • 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
• Related to an ADR discussion, but what can come after the code freeze?
  • No
    • New features
  • 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
• SasModels and SasData feature releases planned

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
• Citing sasview
  • SasView: https://github.com/SasView/sasview/pull/3918 - Jeff to merge - can always move in the future
  • SasModels: https://github.com/SasView/sasmodels/pull/709 - Sujaya to review
  • SasData: https://github.com/SasView/sasdata/pull/200 - Sujaya to review

ADRs

• In review:
  • https://github.com/orgs/SasView/discussions/3171#discussioncomment-15497631: Linter - to be proposed at next biweekly meeting
• Won't be its own ADR:
  • https://github.com/orgs/SasView/discussions/3511: Use web browser instead of built-in window - Closed
• 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
  • 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

AOB?

• Wojtek to co-supervise student this summer (MCR-ALS time-resolved analysis): Candidate interviews this week
• 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
• GSC group: Chris taking over?