Editing Online Developer Meeting (2024-02-27)
Jump to navigation
Jump to search
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 4: | Line 4: | ||
== Today's topics == | == Today's topics == | ||
* Status of 9.1 Release | * Status of 9.1 Release | ||
** Are there remaining blocker bugs? | ** Are there remaining blocker bugs? | ||
** Do we issue a second release candidate (RC2)? | ** Do we issue a second release candidate (RC2)? | ||
* How to handle pull requests for the mirror on GitHub? | |||
* Common id tag for developer of Octave packages in AppStream Metainfo files? | * Common id tag for developer of Octave packages in AppStream Metainfo files? | ||
** Should they use a different tag from the identifier of core Octave? See [https://savannah.gnu.org/patch/?10434 core patch] and [https://github.com/gnu-octave/octave-doctest/pull/286 package change/discussion] | ** Should they use a different tag from the identifier of core Octave? See [https://savannah.gnu.org/patch/?10434 core patch] and [https://github.com/gnu-octave/octave-doctest/pull/286 package change/discussion] | ||
** Conclusions: no strong feelings. Each package should generally decide what they want: if they feel that | ** Conclusions: no strong feelings. Each package should generally decide what they want: if they feel that `id="org.octave"` and `<name>Octave Community</name>` describes their community, that's probably fine. If in doubt, just ask. | ||
== Previous topics == | == Previous topics == |