Table of Contents

Weekly sprints

Minutes

October, Thursday 8th 2009

Week summary

So anybody could edit its own dataflow within or without OpenAlea.

future works

Discussion

pair programming

October, Thursday 15th 2009

presentation

October, Friday 16th 2009

Week summary

Thomas

Eric

Daniel

Christophe

presentation

October, Thursday 22th 2009

presentation

December, Friday 4th 2009

Week summary

Christophe

Daniel

Eric

January, Thursday 7th 2010

New Release Mindstorming 07/01/2010 15:10

The release :

We plan a new release * Stage 1: Solve incompatibilities with boost and python 2.6.4. * Stage 2 : Mingw + qt4.6 Compile in windows and qt4.6 mac * Stage 3 : Openalea trunk is unstable. * Stage 4 : Menus are a mess

Pb : where do we put the new versions of packages. In the installer we can specify sites. If we put new packages on the VPlants site we can develop without impacting the users.

Strategy:

* Solve stage 1. * Work on stage 3 (today!)

Documentation

Thomas restructured the documentation. * each package has a sphinx documentation. * removed automatic reference guide by sphinx (for various reasons, like better control of sphinx, not documentating undisclosable stuff). * There's a metainfo.ini file read by both setup.py and the sphinx conf file. There's a PEP about uniformising metainfo. Maybe change ”.ini” to ”.cfg”.

Today

* Work on stabilizing trunk. * Work on the release (CP : work out a way to simplify the release process).

March, Wed 24th 2009

roadmap:

  1. documentation: sphinx, wiki, tutoriaux
  2. development: code review, functionalities(numpy/pylab, alinea, mtg/plantframe)
  3. release manager: continous integration, schedule(win64/32, fedora12/13, ubuntu 9.10/Mac 10.6) script to automatic install/dependencies
  4. package model vs Package development, citation, formalism, integrate oa installer within PM/version managment.

July, Thursday 22th 2010

Test session

For the next week :

Documentation session

July, Thursday 29th 2010

Test session

Documentation session