Latest revision |
Your text |
Line 6: |
Line 6: |
| * Meet and greet 5 minutes before meeting (audio testing). | | * Meet and greet 5 minutes before meeting (audio testing). |
|
| |
|
| * Performance over time (Arun, Rik)
| |
| ** [https://octave.discourse.group/t/a-small-benchmark-for-interpreted-code-for-three-versions-of-octave/2531/4 Discourse thread for background]
| |
| ** Analysis and profiling of existing code base -- share and solicit experiences.
| |
| ** Performance benchmark to track speed over time as part of CI?
| |
|
| |
|
| * GSoC: call for mentors (Nir/Kai)
| |
| ** Interesting mentors should write to Nir or Kai before: 2022-05-06, ideally before.
| |
| ** Final deadline (to the sponsor) is May 12.
| |
|
| |
| * Octave 7.1.0 post-release remarks:
| |
| ** Overall time from merge of default to stable (2021-11-24) until release of version 7.1.0 (2022-04-06): approx. 4 months
| |
| *** Why does it take us so long for the last couple of releases?
| |
| *** Should we start the release process earlier?
| |
| ** A couple of bugs have been solved on the stable branch since the release. Last time we released 6.2.0 pretty early after 6.1.0. Should we do the same again?
| |
| ** Regressions that should probably be solved before a potential 7.2.0:
| |
| *** bug {{bug|62308}}: use of octave::feval causes error: function '...' not found
| |
| *** patch {{patch|10200}}: wrong axes using stairs in subplot --- This affects a lot more plotting functions besides stairs. They always plot into <code>gca</code> and ignore the input axes handle.
| |
| *** others?
| |
|
| |
| * Wikipedia updates - minor updates needed to bring up to date.
| |
| ** see https://octave.discourse.group/t/octave-wikipedia-pages/2600/1
| |
|
| |
|
| == Previous topics == | | == Previous topics == |
Line 32: |
Line 12: |
|
| |
|
| === Octave 7 RC 2 === | | === Octave 7 RC 2 === |
| | |
| * No major bugs remain, next will be final release. | | * No major bugs remain, next will be final release. |
| ** Done! jwe uploaded 7.1 on 2022-April-06. | | * Bug {{bug|62207}} "segfault in bug-35881/bug-35881.tst in 32-bit ARM and MIPS" appeared. But maybe not a blocker, as only 32-bit ARM and MIPS seems affected. No Octave maintainer can reproduce due to missing hardware. |
| * <strike>Bug {{bug|62207}} "segfault in bug-35881/bug-35881.tst in 32-bit ARM and MIPS" appeared. But maybe not a blocker, as only 32-bit ARM and MIPS seems affected. No Octave maintainer can reproduce due to missing hardware.</strike> Was solved and tested on the platforms.
| |
|
| |
|
| === NumFOCUS === | | === NumFOCUS === |
|
| |
|
| * https://octave.discourse.group/t/apply-for-numfocus-sponsoring/2328 | | * https://octave.discourse.group/t/apply-for-numfocus-sponsoring/2328 |
| ** Kai reached out for them. Form filled out with email confirmation. Application deadline July 15 (Round 2), Notifications will be sent on or before: August 31 (Round 2). Major issue: Missing Code of Conduct. | | ** Kai will reach out for them. |
|
| |
|
| === Bus factor problem, revisited === | | === Bus factor problem, revisited === |
Line 46: |
Line 26: |
| * FossHost accepting applications again [https://fosshost.org/] | | * FossHost accepting applications again [https://fosshost.org/] |
| ** <strike>Arun will reach out for them.</strike> Done! | | ** <strike>Arun will reach out for them.</strike> Done! |
| ** As of 2022-April-03, Fosshost has offered amd64 and arm64 servers for Octave's use as web servers and buildbots: https://octave.discourse.group/t/project-infrastructure-discussion/1938/14. When it is finalized, Fosshost will notify the Octave devs (Kai?) directly via email. | | ** As of 2022-April-01, Fosshost has offered amd64 and arm64 servers for Octave's use as web servers and buildbots: https://octave.discourse.group/t/project-infrastructure-discussion/1938/12. The discussion is currently ongoing. |
|
| |
|
| === Octave 8 === | | === Octave 8 === |
Line 56: |
Line 36: |
| === GSoC 2022 === | | === GSoC 2022 === |
|
| |
|
| * <strike>[https://octave.discourse.group/t/gsoc-2022-symbolic-package-project/2396/3 Maintainers of symbolic package unresponsive]. If no communication gets established by the weekend, this project will be dropped to avoid applicants putting energy in this.</strike> | | * [https://octave.discourse.group/t/gsoc-2022-symbolic-package-project/2396/3 Maintainers of symbolic package unresponsive]. If no communication gets established by the weekend, this project will be dropped to avoid applicants putting energy in this. |
|
| |
|
| === Package problems === | | === Package problems === |