Online Developer Meeting (2023-08-22): Difference between revisions

From Octave
Jump to navigation Jump to search
Tags: Mobile edit Mobile web edit
(Add some notes from meeting)
Β 
Line 5: Line 5:
* GSoC updates? GSoC's standard contribution period is supposed to end on 28 August.
* GSoC updates? GSoC's standard contribution period is supposed to end on 28 August.
* Octave 8.3.0 has been released
* Octave 8.3.0 has been released
** Smooth release so far
** Rolling releases started to update without new issues
* Remove installer for Octave for Windows 32-bit?
* Remove installer for Octave for Windows 32-bit?
** Probably remove link from download page
** See: https://octave.discourse.group/t/proposal-to-remove-8-3-0-32-bit-windows-installer-link/4763


== Previous topics ==
== Previous topics ==

Latest revision as of 16:25, 25 September 2023

Today's topics[edit]

Previous topics[edit]

  • Release of Octave 8.3.0?
    • Approximately 22 bugs fixed on the stable branch since the release of Octave 8.2.0 (plus additional updates on MXE Octave).
    • A new release will be made when jwe comes around to it. No release candidate.
  • Octave online community event
    • Online poll indicates best time would be October or November, 2023
    • Brainstorm event goals (social interaction, specific coding projects, something else?), duration.
    • Rik will post a thread on discourse with a poll for possible topics.
  • OctConf 2024
    • Online poll indicates best time would be April-June or October-November, 2024
    • Discuss conference goals, duration, location
    • Rik will post a thread on discourse with follow-up questions. (E.g., location, weekend or weekdays, attach to other community meetings)
  • Move MXE Octave builds to default to UCRT? See: Thread on Discourse
    • Switch default branch of MXE Octave to UCRT to check if it builds and works.
    • Announce that Octave 9 will require Windows 8.1 or newer for the distributed Windows binaries.
  • GSoC updates
  • Docker images for weekly(?) built versions of Octave from the stable and the default branch could be useful for Octave package developers that would like to catch early if their package needs to adapt for API changes in core Octave.
    • It needs to be made clear to everyone that these images are expected to break at any point. That shouldn't reflect on the image of Octave's quality in general.
    • See: should we host devel and stable images?

See also[edit]