Editing Online Developer Meeting (2022-02-22)

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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 8: Line 8:
=== Release process of Octave 7.1 ===
=== Release process of Octave 7.1 ===


* Blocking issues: 8 open bugs targeting 7.0.90, 3 marked as "ready for test" (see [https://octave.space/savannah/# Savannah overview on octave.space])
* Blocking issues: 9 bugs targeting 7.0.90, 3 marked as "ready for test" (see [https://octave.space/savannah/# Savannah overview on octave.space])
* Good progress on some of the blocking issues by jwe. Most important remaining ones:
* Good progress on some of the blocking issues by jwe. Most important remaining ones:
** bug {{bug|61788}}: arrays of type int16 contain wrong numbers
** bug {{bug|61788}}: arrays of type int16 contain wrong numbers
Line 17: Line 17:
** bug {{bug|61813}}: memory management bug when calling MEX that returns an output
** bug {{bug|61813}}: memory management bug when calling MEX that returns an output
*** @jwe check in a fix that will also revert to copying data in the .mex interface (less efficient, but also the way it has always been done until now) unless Octave is compiled with C++17 pmr.
*** @jwe check in a fix that will also revert to copying data in the .mex interface (less efficient, but also the way it has always been done until now) unless Octave is compiled with C++17 pmr.
*** This also avoids the <code>malloc</code>-<code>operator delete[]</code> mismatch.
*** Confirmed fixed now.
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file
*** Lower priority, only 32-bit (only on Windows?). Maybe a compiler bug?
*** Lower priority, only 32-bit (only on Windows?). Maybe a compiler bug?
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: