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 3: |
Line 3: |
|
| |
|
| == Today's topics == | | == Today's topics == |
| * Status of 9.1 Release | | * foo |
| ** Are there remaining blocker bugs? -- None. In case of issues, a version 9.2 could be released early. | | * bar |
| ** Do we issue a second release candidate (RC2)? -- No RC2. jwe will proceed to create a release tarball for Octave 9.1 and the Windows installers shortly.
| |
| * 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]
| |
| ** Conclusions: no strong feelings. Each package should generally decide what they want: if they feel that <code>id="octave.org"</code> and <code><name>Octave Community</name></code> describes their community, that's probably fine. If in doubt, just ask.
| |
| * How to handle pull requests for the mirror on GitHub?
| |
| * New bug reports on Savannah for packages should be tagged by the package name in parenthesis at the start of the report title. E.g., "(statistics) some error" (i.e., no longer prepend with "[octave forge]"). Also, set the report category to "Octave package". Try to CC package developers.
| |
|
| |
|
| == Previous topics == | | == Previous topics == |