Difference between revisions of "Online Developer Meeting (2020-07-07)"

From Octave
Jump to navigation Jump to search
(→‎Community Infrastructure (Kai): https://planet.octave.org)
(→‎See also: Announce next meeting.)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
* Date: [https://lists.gnu.org/archive/html/octave-maintainers/2020-06/msg00134.html Tuesday, July 7, 2020 @ 14:00 UTC]
 
* Date: [https://lists.gnu.org/archive/html/octave-maintainers/2020-06/msg00134.html Tuesday, July 7, 2020 @ 14:00 UTC]
* Location: https://meet.jit.si, exact URL will be announced on maintainers@octave.org and [[IRC]] an hour before the meeting.
+
* Location: https://meet.jit.si/octave-dev-2020-07-07
  
 
== Todays topics ==
 
== Todays topics ==
Line 7: Line 7:
  
 
=== Octave 6 release status ===
 
=== Octave 6 release status ===
 +
 +
* We should create a first release candidate (RC) Octave '''6.0.90''' soon.  Base for discussing and working on further bug findings.
 +
** Update gnulib before RC
 +
** Tag some cset on stable.
 +
** Build MS Windows binaries.
 +
** Upload to https://alpha.gnu.org/gnu/octave/ .
 +
 +
* Still hard to fix blocking bugs
 +
** Build (RC) anyway!
 +
** crashes during doc graphics creation seem to be fixed (bug {{bug|56952}})
 +
** still elusive crashes while running the test suite on the build bots (bug {{bug|57591}}) -> Maybe the broader user base of an RC can shed some light on "real-life frequency" of these crashes.
 +
** possible background: interaction between graphics system and interpreter is different from interaction of rest of GUI with the interpreter. Possibly resolvable by a copy-on-write approach for graphics objects (postponed to Octave 7)
 +
 +
* Other important bugs
 +
** calling script from nested functions (bug {{bug|58691}} fixed)
 +
** empty list creation if one element is not assigned (bug {{bug|58686}} not a blocker)
 +
 +
* Try to tackle bugs with debuggers
 +
** valgrind slow
 +
** <code>-fsanitize=thread</code> in memory and faster
 +
 +
* Before Octave 6.1.0 release, discharge MS Windows 10 Malware Detection Systems (e.g. upload to https://www.virustotal.com/)
  
 
=== Community Infrastructure ([[User:siko1056|Kai]]) ===
 
=== Community Infrastructure ([[User:siko1056|Kai]]) ===
  
* [https://octave.discourse.group/ Discourse for GNU Octave]
+
* [https://octave.discourse.group/ Discourse for GNU Octave] '''YES, we give it a try!''' 😁
 
** Replacement for mailing-lists (help@octave.org and maintainers@octave.org) and https://planet.octave.org
 
** Replacement for mailing-lists (help@octave.org and maintainers@octave.org) and https://planet.octave.org
** Badge system
+
*** Leave old mailing-lists as they are now, but no longer actively advertise them.
 +
*** '''TODO:''' Advertise Octave Discourse <strike>on Octave homepage</strike> and announce on mailing-lists
 +
** Badge system, will stay active for the start
 
** Discussions are welcome
 
** Discussions are welcome
 +
*** Max. image upload size: (Yes) There is not a restriction in the file size, but in the megapixels <code>max image megapixels = 40</code> and dimension <code>max image width = 690</code>, <code>max image height = 500</code>.
 +
*** Max. edit time: Yes, there is <code>editing grace period = 300</code> seconds, but admins can edit any post.
 +
*** Possible exit strategy in case we don't like Discourse?
 +
**** Return to still active mailing-lists always possible.
 +
**** Disable Posting in that Forum, try to leave it as archive.  If Discourse does not allow archives, we can export the SQL database and try to host the knowledge on some other facility.
 
** See also https://octave.discourse.group/t/do-we-want-to-adopt-discourse/39
 
** See also https://octave.discourse.group/t/do-we-want-to-adopt-discourse/39
* Hosting Octave main website on "https://www.octave.org" (jwe's dreamhost.com account) rather than "https://www.gnu.org/software/octave/", see [[Project Infrastructure]].
+
* (No time left, maybe next time) <strike>Hosting Octave main website on "https://www.octave.org" (jwe's dreamhost.com account) rather than "https://www.gnu.org/software/octave/", see [[Project Infrastructure]].
** Updating Octave's main website is pain ([https://en.wikipedia.org/wiki/Concurrent_Versions_System CVS], see [https://hg.octave.org/web-octave/file/tip/Makefile Makefile])
+
** Updating Octave's main website is pain ([https://en.wikipedia.org/wiki/Concurrent_Versions_System CVS], see [https://hg.octave.org/web-octave/file/tip/Makefile Makefile])</strike>
  
 
== Ideas for next meeting ==
 
== Ideas for next meeting ==
Line 24: Line 53:
 
== See also ==
 
== See also ==
  
* Next meeting: TBA
+
* Next meeting: [[Online Developer Meeting (2020-07-28)]]
 
* Last meeting: [[Online Developer Meeting (2020-06-09)]]
 
* Last meeting: [[Online Developer Meeting (2020-06-09)]]
  
 
[[Category:2020]]
 
[[Category:2020]]
 
[[Category:Meetings]]
 
[[Category:Meetings]]

Latest revision as of 03:23, 28 July 2020

Todays topics[edit]

  • Meet and greet 5 minutes before meeting (audio testing).

Octave 6 release status[edit]

  • We should create a first release candidate (RC) Octave 6.0.90 soon. Base for discussing and working on further bug findings.
  • Still hard to fix blocking bugs
    • Build (RC) anyway!
    • crashes during doc graphics creation seem to be fixed (bug #56952)
    • still elusive crashes while running the test suite on the build bots (bug #57591) -> Maybe the broader user base of an RC can shed some light on "real-life frequency" of these crashes.
    • possible background: interaction between graphics system and interpreter is different from interaction of rest of GUI with the interpreter. Possibly resolvable by a copy-on-write approach for graphics objects (postponed to Octave 7)
  • Other important bugs
    • calling script from nested functions (bug #58691 fixed)
    • empty list creation if one element is not assigned (bug #58686 not a blocker)
  • Try to tackle bugs with debuggers
    • valgrind slow
    • -fsanitize=thread in memory and faster

Community Infrastructure (Kai)[edit]

  • Discourse for GNU Octave YES, we give it a try! 😁
    • Replacement for mailing-lists (help@octave.org and maintainers@octave.org) and https://planet.octave.org
      • Leave old mailing-lists as they are now, but no longer actively advertise them.
      • TODO: Advertise Octave Discourse on Octave homepage and announce on mailing-lists
    • Badge system, will stay active for the start
    • Discussions are welcome
      • Max. image upload size: (Yes) There is not a restriction in the file size, but in the megapixels max image megapixels = 40 and dimension max image width = 690, max image height = 500.
      • Max. edit time: Yes, there is editing grace period = 300 seconds, but admins can edit any post.
      • Possible exit strategy in case we don't like Discourse?
        • Return to still active mailing-lists always possible.
        • Disable Posting in that Forum, try to leave it as archive. If Discourse does not allow archives, we can export the SQL database and try to host the knowledge on some other facility.
    • See also https://octave.discourse.group/t/do-we-want-to-adopt-discourse/39
  • (No time left, maybe next time) Hosting Octave main website on "https://www.octave.org" (jwe's dreamhost.com account) rather than "https://www.gnu.org/software/octave/", see Project Infrastructure.
    • Updating Octave's main website is pain (CVS, see Makefile)

Ideas for next meeting[edit]

Topic suggestions[edit]

See also[edit]