Code Sprint (2015-12-12): Difference between revisions

From Octave
Jump to navigation Jump to search
(Create page)
 
(Create page)
Line 1: Line 1:
The worldwide Octave community will be holding a code sprint this December.


'''When:''' December 12th, 14:00 UTC.
'''Where:''' Octave IRC channel, #octave.  See [[IRC]].


 
A code sprint is an opportunity for programmers to get together for both coding and socializing.
The following bugs must be fixed prior to the next release. See also the [[4.0 Release Checklist]] .
We will have some goals, the sprint topics shown below, to guide our sprint, but anyone is welcome to hang out and work on their own special topic.
 
There will be multiple Octave Maintainers attending so this is also a good chance to get introduced to the Octave code base and how to make patches for it.
Sign up for a bug by filling in the Owner field so people won't duplicate each other's work.
In order to contribute you should have installed Mercurial, fetched the development sources, and have successfully built your own local copy of Octave.
 
See [http://www.gnu.org/software/octave/get-involved.html Getting Involved].
Use <pre><strike> ... </strike></pre> to cross an item off the list when it has been done. Add <pre>WON'T FIX</pre> and the strike through tag for any bugs that will not be fixed in this round.


== Sprint Topics ==
== Sprint Topics ==
[[2015 Code Sprint/topic1]]
# [[Refactor C++ code that uses print_usage() and error() to resemble m-files]]
# [[Add BIST tests for octave functions written in C++]]
# [[Remove class of function from documentation strings]]
# [[Move some ODE package functions from Octave-Forge to core]]
# Add to this list


== Attendees ==
== Attendees ==
* Rik


[[Category:Releases]]
[[Category:Releases]]

Revision as of 18:54, 4 December 2015

The worldwide Octave community will be holding a code sprint this December.

When: December 12th, 14:00 UTC. Where: Octave IRC channel, #octave. See IRC.

A code sprint is an opportunity for programmers to get together for both coding and socializing. We will have some goals, the sprint topics shown below, to guide our sprint, but anyone is welcome to hang out and work on their own special topic. There will be multiple Octave Maintainers attending so this is also a good chance to get introduced to the Octave code base and how to make patches for it. In order to contribute you should have installed Mercurial, fetched the development sources, and have successfully built your own local copy of Octave. See Getting Involved.

Sprint Topics

  1. Refactor C++ code that uses print_usage() and error() to resemble m-files
  2. Add BIST tests for octave functions written in C++
  3. Remove class of function from documentation strings
  4. Move some ODE package functions from Octave-Forge to core
  5. Add to this list

Attendees

  • Rik
Retrieved from "https://wiki.octave.org/wiki/index.php?title=Code_Sprint_(2015-12-12)&oldid=6920"