1,072
edits
Online Developer Meeting (2023-12-19): Difference between revisions
Online Developer Meeting (2023-12-19) (edit)
Revision as of 22:10, 19 December 2023
, 19 December 2023Add assignments to tasks
ArunGiridhar (talk | contribs) (→Today's topics: T) Tags: Mobile edit Mobile web edit |
m (Add assignments to tasks) |
||
| Line 5: | Line 5: | ||
* Octave 9 remaining release activities | * Octave 9 remaining release activities | ||
** Blocking bugs | ** Blocking bugs | ||
*** Change in BLAS/LAPACK condition number for `inf (2,2)`. Should we disable tests for this feature to avoid confusion that something is wrong with Octave, while we work on a strategy for this? ''' | *** Change in BLAS/LAPACK condition number for `inf (2,2)`. Should we disable tests for this feature to avoid confusion that something is wrong with Octave, while we work on a strategy for this? '''Rik to create bug report, Change BIST tests to use %!xtest with new bug number, Investigate long-term returning 0 for rcond of Inf matrix''' | ||
*** Windows Terminal problems | *** Windows Terminal problems | ||
**** Apparently the Developer option fix may not be readily visible for everyone? see https://octave.discourse.group/t/bug-octave-freezes/5097/9 | **** Apparently the Developer option fix may not be readily visible for everyone? see https://octave.discourse.group/t/bug-octave-freezes/5097/9 | ||
**** Do we have enough detail to create a useful report upstream at https://github.com/microsoft/terminal/issues ? | **** Do we have enough detail to create a useful report upstream at https://github.com/microsoft/terminal/issues ? | ||
** Translation files | ** Translation files '''Rik to ping Marco about Italian translation''' | ||
** First names or abbreviated names in `contributors.in`? '''Rik will follow up with individuals''' | ** First names or abbreviated names in `contributors.in`? '''Rik will follow up with individuals''' | ||
** `-fsanitize` and other checks on code | ** `-fsanitize` and other checks on code | ||
*** Should leaks be analyzed in Discourse thread or a Savannah bug report? '''Discourse to start, bug afterwards''' | *** Should leaks be analyzed in Discourse thread or a Savannah bug report? '''Discourse to start, bug afterwards''' | ||
** Update of Copyright statements. '''jwe to do this''' | |||
** Approximate date for release candidate | ** Approximate date for release candidate | ||
* Octave coding guidelines | * Octave coding guidelines | ||
** Need refresh as recommendations are out of date | ** Need refresh as recommendations are out of date | ||
*** Line length | *** Line length '''Re-write from hard limit (80) to user preference as long as code is clear. Clear code can sometimes mean putting all of the statement on one line so it is one unit''' | ||
*** Break return type of function and put on separate line for class methods within class definition? '''Original reason no longer applies, so use judgment based on e.g. length of return type l''' | *** Break return type of function and put on separate line for class methods within class definition? '''Original reason no longer applies, so use judgment based on e.g. length of return type l''' | ||
*** `enum`, `struct` style not particularly clear or documented | *** `enum`, `struct` style not particularly clear or documented. '''Document that style should be like functions with opening '{' not indented but appearing on its own line''' | ||
*** #ifdef indentation and styling '''No clear preference''' | *** #ifdef indentation and styling '''No clear preference''' | ||