Editing Online Developer Meeting (2021-04-27)
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 15: | Line 15: | ||
* Which branch should the buildbots use? | * Which branch should the buildbots use? | ||
** http://buildbot.octave.org:8010/ (jwe) | ** http://buildbot.octave.org:8010/ (jwe) | ||
*** | *** Not really sure about a definite decision | ||
** https://buildbot.octave.space/ (Kai) | ** https://buildbot.octave.space/ (Kai) | ||
*** General move to "release" branch (probably May) | *** General move to "release" branch (probably May) | ||
Line 25: | Line 24: | ||
* Find out how to trigger a build on changes in two repositories? | * Find out how to trigger a build on changes in two repositories? | ||
** Untested idea: https://github.com/gnu-octave/octave-buildbot/pull/9/files | ** Untested idea: https://github.com/gnu-octave/octave-buildbot/pull/9/files | ||
=== 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 64: | Line 38: | ||
*** https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017 | *** https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017 | ||
General consensus was to stay with C++11 until a "killer application" shows up that | General consensus was to stay with C++11 until a "killer application" shows up that would really changing to a newer standard. | ||
=== Short introduction: SavannahAPI === | === Short introduction: SavannahAPI === | ||
Line 95: | Line 69: | ||
== Previous topics == | == Previous topics == | ||
=== Octave 7 === | === Octave 7 === |