Talk:What to do for a release
Certain embedded docs need re-validation prior to each release:
- The license from the Help -> about box (was the "'Ty Coon' customizing your license" example at the end trimmed off?)
- the list of Contributing Authors in the Help -> About
- Tip of the Day (tips.xml) for obsoleted information
- the "Welcome to Gramps!" gramplet text for obsoleted information
Should these be included in the checklist?
Bamaustin (talk) 14:41, 3 November 2022 (UTC)
Bamaustin (talk) 22:08, 6 April 2024 (UTC)
Nick replies about updating the SourceForge assets from https://gramps.discourse.group/t/12-days-since-5-2-1-and-no-word-on-debian-asset/5229/5
> Thanks. I’ve uploaded the Windows AIO and the SHA256SUMS.
>
> There is a flag on the file information where we can set the default download for each OS.
Should the PyPI repository upload workflow be added to the GitHub and SourceForge?
(documentation feature request: https://gramps-project.org/bugs/view.php?id=13933)
Doug Blank pointed out the status of the PyPI upload can be verified at: https://github.com/gramps-project/gramps/actions/workflows/pypi-upload.yml
Are there similar validation/status links that could be added that the end the upload workflows for GitHub and SourceForge?
