Difference between revisions of "Developers/Release 0.8.0"
Jump to navigation
Jump to search
(LTO) |
(py 3.9 deprecates some functions) |
||
Line 11: | Line 11: | ||
* what currently open issues should be considered "blockers" for a release ? | * what currently open issues should be considered "blockers" for a release ? | ||
** | ** "Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions, deprecated in Python 3.9" https://bugzilla.redhat.com/show_bug.cgi?id=2245598 | ||
** Possibly some other Python2 / 3 compatibility and deprecation issues, | |||
** random weird issues that always seem to come from Win* users running weird combinations of hardware / firmware, mostly USB ? | ** random weird issues that always seem to come from Win* users running weird combinations of hardware / firmware, mostly USB ? | ||
** -flto maybe breaks builds (driver list gets optimized out ? forget the details) on some distros ? | ** -flto maybe breaks builds (driver list gets optimized out ? forget the details) on some distros ? |
Revision as of 18:20, 23 October 2023
This is an attempt at a checklist for the "next release" - as of 2023/10, for sigrok-cli this would be either 0.7.3 or 0.8.0 (maybe the latter would be more appropriate given that 0.7.2 was over 2 years ago ?). Other subprojects have different numbers e.g. last libsigrok was 0.5.2 .
Most of this is intended to expand on the main release guidelines here https://sigrok.org/wiki/Developers/Release_process
- what platforms "must work" ?
- linux is the most tested based on IRC traffic, but maybe we can explicitly list distros to test ?
- win : would be nice to have a list of people we can ping to get them test a build
- osx : no idea, no user reports in IRC
- *BSD : no idea, no user reports in IRC
- what currently open issues should be considered "blockers" for a release ?
- "Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions, deprecated in Python 3.9" https://bugzilla.redhat.com/show_bug.cgi?id=2245598
- Possibly some other Python2 / 3 compatibility and deprecation issues,
- random weird issues that always seem to come from Win* users running weird combinations of hardware / firmware, mostly USB ?
- -flto maybe breaks builds (driver list gets optimized out ? forget the details) on some distros ?
- what external projects depend on sigrok components or bindings ? does it actually matter ?
- Pulseview
- smuview
Transports (this would be better presented in a matrix format with feature vs OS) :
- serial (native/USB-CDC)
- USB (non-serial)
- USB
- TCP/IP
- GPIB (probably just linux ?)
- VXI ?
checklist test
title