Editing Online Developer Meeting (2021-04-27)
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 9: | Line 9: | ||
* Which changes should go on which branch? | * Which changes should go on which branch? | ||
* Which branch should the buildbots use? | * Which branch should the buildbots use? | ||
=== String class strategy === | === String class strategy === | ||
* Strategy for transition to string class syntax (incompatible to current double-quoted character vectors in Octave)? | * Strategy for transition to string class syntax (incompatible to current double-quoted character vectors in Octave)? | ||
=== C++17 === | === C++17 === | ||
Line 59: | Line 19: | ||
* Updates: https://octave.discourse.group/t/using-c-17-features/1026 | * Updates: https://octave.discourse.group/t/using-c-17-features/1026 | ||
* Allow using more modern C++ dialects (C++17 STL std::filesystem or boost::filesystem)? | * Allow using more modern C++ dialects (C++17 STL std::filesystem or boost::filesystem)? | ||
=== Short introduction: SavannahAPI === | === Short introduction: SavannahAPI === | ||
Line 89: | Line 43: | ||
What is the best approach to resolving this? | What is the best approach to resolving this? | ||
* <strike>A new wiki page</strike> so one with permission can see all the "easy closes". | * <strike>A new wiki page</strike> so one with permission can see all the "easy closes". (Please reuse the [[Short projects]] page for this purpose, which is currently unmaintained.) | ||
* Pinging bugs/patches for a status update. (Always a good idea and this is basically what happens very slowly. It would be great to see more volunteers triaging the bug and patch trackers.) | |||
* Pinging bugs/patches for a status update. | |||
== Previous topics == | == Previous topics == | ||
=== Octave 7 === | === Octave 7 === |