-
Notifications
You must be signed in to change notification settings - Fork 49
DevNotes_02Jun2026
-
Technical meeting updates - (Sharp/Krzywon)
- Technical meetings occur fortnightly on Fridays in alternate weeks from this meeting
-
Refactoring project updates
- Refactoring Hackathon II will take place 3-5 June
- Last Minute updates?
-
SASBDB integration project (Wojciech)
-
Generic Scattering Calculator redesign working group
- Meeting held just prior to this one
- the webpage has been updated
-
Sasmodels working group (refactoring project and marketplace vs core etc) (Paul and Wojciech)
- Wiki pages generated https://github.com/SasView/sasview/wiki/DevNotes_ModelsWG
- Kickoff meeting delayed
-
Code freeze started on 15th May.
- Release checklist
- New versions for SasModels (1.0.13) and SasData (0.12.0)
- The latest alphas available for testing:
- sasmodels just got bumped to alpha3. the bundle artifacts for SasView alpha 2 are using sasmodels alpha2. Do we need an alpha3 release of Sasview?
- Please download and test. The hope is to be able to release a beta 1 very soon!
-
Timeline:
- Mid June: end of alpha testing and full code freeze - a release candidate will follow this.
- End of June: full release
-
Rules:
- only bug fixes relevant to new features added
- no new models
-
MultiSlicers by @jellybean2004 in
#3970 -
SideDistribution by @jellybean2004 in
- #3962 — Size Distribution calculator clean up (cleanup/type hints for new SD perspective shipping in 6.2.0)
- #3963 — Single kernel call for volume and intensity (fixes #3418, SD bug fix; depends on #3962)
- #3965 — Adds PDF report for Size Distribution (new feature for SD perspective in 6.2.0)
- #3967 — Fix report preview background (fixes #3964, dark mode regression — recent issue) APPROVED
-
auto upload binaries during CI if a tagged branch (needed for releases?) by @krzywon in
- #3932 — Upload Binaries On Tag (CI release workflow — could be needed for release process itself)
-
Is this for 6.2?
- How should we acknowledge contributing institutions? Do we continue to use logos? If so how do we decide?
- The suggestion we currently have is:
- We will remove the logos from the SasView application and rephrase the wording to avoid listing institutions.
- We will add lists of affiliations to the people page on sasview.org, alongside a separate list of contributor camp hosts.
- We will also update the grants section of the people page, and the contributors.tsv file in the SasView repo.
- We currently have around 30 contributing institutions, over 20 of which are universities.
- General consensus is that having full lists of institutions and/or logos on sasview.org is easier than in the application itself.
- Please let us know of any grants that we may be missing.
-
First hotel option: Hermitage
- nearby (10 min walk)
- closer to restaurants
-
considering another hotel option: Grand Hotel
- cheaper
- arguably better amenities
- decent place
- bit further away (20 min walk)
- metro station nearby
-
Defining the Release Process and the Release Manager Role: needs discussion
-
The Defining the Release Process and the Release Manager Role ADR is an "overarching" ADR, that contains several points within it that are ADRs themselves.
https://github.com/SasView/sasview/wiki/DevNotes_HelpDesk
- Covered through June (need summer coverage)
- 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