Online Developer Meeting (2021-09-28): Difference between revisions

Copy topics from last meeting. Add two topics for this meeting.
(Create page.)
 
(Copy topics from last meeting. Add two topics for this meeting.)
Line 1: Line 1:
* Date: Tuesday, September 28, 2021 @ 18:00 UTC
* Date: Tuesday, September 28, 2021 @ 18:00 UTC
* Location: https://meet.jit.si/octave-dev-2021-09-28
* Location: https://meet.jit.si/octave-dev-2021-09-28


== Todays topics ==
== Todays topics ==
Line 6: Line 7:
* Meet and greet 5 minutes before meeting (audio testing).
* Meet and greet 5 minutes before meeting (audio testing).


=== First topic ===
=== Octave 6.4.0? ===
 
* Last(?) Octave 6 release?
* Background: 12 changes on the stable branch (~10 on the release branch of MXE Octave) since the last release. Most important ones:
** Octave GUI doesn't start for some Windows users. Bug in Qt 5.14 that is fixed in Qt 5.15.
** Crash to desktop fixed in Octave core ([https://savannah.gnu.org/bugs/?61191 bug #61191]).
** Crash to desktop fixed in librsb ([https://savannah.gnu.org/bugs/?60042 bug #60042], only affects Windows bundle).
** Command line arguments with parameters (e.g. <code>--path</code>) can't be combined with <code>--gui</code> ([https://savannah.gnu.org/bugs/?60886 bug #60886]).
 
=== Approximate release date for Octave 7? ===
 
* Last few cycles: merge to stable and release date of first stable version:
** 6.x: merge to stable: 2020-02-17 --- release: 2020-11-26 (~ 9.5 month)
** 5.x: merge to stable: 2018-12-20 --- release: 2019-02-23 (~ 2 month)
** 4.4.x: merge to stable: 2018-04-04 --- release: 2018-04-30 (< 1 month)
** 4.2.x: merge to stable: 2016-09-28 --- release: 2016-11-13 (~ 1.5 month)
 
=== CamelCase in Octave functions? ===
 
* What is our current stance on that?
 
 
== Previous topics ==
:''The following items were not discussed.  Just some links to progress on those items are displayed.''
 
=== Switch this meeting to more casual format ===
 
* In the future notes of the talks will be added to this wiki in a more sparse fashion.
 
=== liboctave ===
 
* Make more use of STL
* Not all liboctave components can be replaced by STL containers, as the ND-indexing is not supported.
* <code>string_vector</code> class probably replaceable by STL containers.
 
=== Tips for Octave C++ code writers ===
 
Such as packages, toolboxes, etc.
 
* Prefer <code>OCTAVE_LOCAL_BUFFER</code> over heavy-weight <code>Array</code> object to store results of (Fortran-) library calls.
* Prefer <code>octave_value</code> type variables over internal data structures.
** Examples: Function handle class and Range class.
 
=== For package maintainers ===
 
* Do not use <code>error_state</code> anymore! https://octave.discourse.group/t/eliminating-use-of-error-state-in-octave-code/1515
* Do not suppress compiler warnings about deprecated features today, those are the bug reports of tomorrow, when it is too late.
 
=== octave namespace ===
 
* jwe made many breaking changes on the default branch moving symbols in the octave namespace, to keep the namespaces tidy.
 
=== Deprecations ===
 
* The operators <code>.+</code>, <code>.-</code>, and <code>**</code> https://octave.discourse.group/t/deprecating-fortran-style-exponent-operator/1516 will be deprecated.
 
=== Trolling ===
 
* In case of trolling behavior of users, please mark the thread, thus a Discourse admin can close the threat and mute the user.
** DO NOT FEED THE TROLL: Any further answer or conversation is most likely a waste of emotions and time.
* Any user violating the usage conditions https://octave.discourse.group/tos#heading--conditions will be muted or removed from the forum entirely.
 
=== Code sprints ===
 
* Wish for more code sprints, e.g.,
** "m_" convention https://octave.discourse.group/t/using-m-prefix-for-member-variables-in-c-classes/1517/17
** Close easy closable bugs [[Short_projects#Easy_Closes]]


== See also ==
== See also ==
216

edits