Skip to content

Linbox Developer Day 1

Clément Pernet edited this page Apr 1, 2017 · 3 revisions

Minutes of the LinBox Developer Day 1 (March 31st 2017)

Ressources

Developper's best practices

Since about a year, we experiment a new development model for the fflas-ffpack library: using the feature branch workflow. (see

In brief this means that

  • commits to master branch are limited to trivial fixes (typos or on liner bug fixes)
  • each new piece of code (bug fix or feature) needs to be developped in a new branch
  • Once the branch is ready, create a pull request for it: thus inviting other developpers to review the branch

The review process include

  • testing the branch on the reviewers machine,
  • reading the diff of the code
  • checking the continuous integration build status

Once everything is ok, the reviewer clicks on the "merge" button, hence merging the branch to master

  • In order to avoid bottlenecks of PRs not being reviewed, we proposed that the author of a PR could himself merge it after and embargo period of a week or two. But ideally it should not be used. This framework is currently only implemented in fflas-ffpack for the moment. Feel free to use it in Givaro and LinBox too!

Work in progress

  • giorgi: fflas-ffpack #67 Modular fails in DEBUG mode
  • giorgi: fflas-ffpack #29 ftrsm with Modular (ftrsm_mp), consistently fails with small modulus (related to #27)
  • lebreton + bruno: [givaro #10](https://github.com/linbox-team/givaro/issues/10]: Harmonization in Modular...<...> (maxCardinality bounds, Compute_t, ... )
  • cdelaplace: debug of the spasm version of Linbox (sorry I have a bug with my user colour)

Pull requests needing review

Work done