-
Notifications
You must be signed in to change notification settings - Fork 48
DevNotes_17Apr2026_Technical
Jeff Krzywon edited this page Apr 14, 2026
·
3 revisions
Next Refactor Hackathons
- Refactor Hackathon I: Mar 16-17
- Refactor Hackathon II: ~June
- Refactor Hackathon III: ~September
- Refactor Hackathon IV: ~December
- Bad Dates:
- ACNS: July 12-16
- 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 (16 open, 10 in draft, 0 approved)
- Discuss:
- Use browser for help: https://github.com/SasView/sasview/pull/3847 - broken unit test
- Release automation: https://github.com/SasView/sasview/pull/3918 - one release automation script that only lives in sasview, or separate scripts for each repo?
- Discuss:
- SasModels (11 open, 5 in draft)
-
SasData (8 open, 6 in draft)
- SasData API: https://github.com/SasView/sasdata/pull/106 - Jeff to get into a mergeable state...
- Proposed code freeze date: May 15, with Alpha1 release on May 18
- What outstanding PRs should be included:
- Remove QtWebEngine
- Parameter sliders
- New models
- 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
Status updates of ongoing projects
- CodeScene and Ruff (Paul S./Jeff)
- CodeScene integration - Wiki In Progress
- Jeff to finish off write up for
Minimal Safety Net - What thresholds should we use for different things?: https://github.com/SasView/sasdata/blob/master/.codescene/code-health-rules.json
- Once write up is finished and thresholds are decided, enable on sasdata
- Jeff to finish off write up for
- CodeScene integration - Wiki In Progress
- Citing sasview
- Sasview.org: https://github.com/SasView/sasview.github.io/pull/32
- 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:
- Ongoing discussion:
- https://github.com/orgs/SasView/discussions/3511: Use web browser instead of built-in window - Assign writer
- New to discuss
- No link: Defining the release process and release manager - Jeff to create discussion
- Some 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?
- 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
- Zenodo generation:
build_tools/release_automation.py, but would need tweaks, the ability to commit changes, and the ability to change release tags - Jeff already working on it, likely never part of the CI - Pypi publishing: Work started in sasdata
- Upload binaries to releases: Already working for nightly build
- Zenodo generation:
- No link: Defining the release process and release manager - Jeff to create discussion
AOB?
- View/Subscribe to the SasView Calendar
- Fortnightly developer's agenda/minutes
- Developer Guides
- Admin Processes and Procedure Notes
- Active Project Pages
- Historical Archive of Obsolete Pages
- Contributor e-Learning Course (free)
- Non Coding contribution needs/projects
- New functionality projects
- acknowledging contributions