Home | Download/Install | Documentation | Packages | Screenshots | News | Forum/Mailing-lists | Contact | GForge

Preparing OpenAlea 1.0

Release 1.0 would happen end of march 2012

Goals

  • A release for Python 2.7 of the last OpenAlea/VPlants/Alinea packages

Features

FIXME

Information about the branches

These branches are stable branches. All bug fix will be developed here and then merged to the trunk.

For merging instructions read Branching and merging.

Packaging Status

The following table summarizes the status of various release-related tasks for each pacakge to be released. The UnitTest can be checked on the continuous integration server.

Br(1) Up(2) MS(7) Egg(3) Src(4) Doc Unit Tests NativeInstallers Comments
packages Complete(5) Uploaded(6) Linux MacOsX Windows .deb .rpm .exe .dmg
OpenAlea
deploy TODO =) TODO
deploygui TODO =) TODO
core TODO =) TODO
scheduler TODO =) TODO
visualea TODO =) TODO
stdlib TODO =) TODO
sconsx TODO =) TODO
misc TODO =) TODO
grapheditor TODO =) TODO
image TODO TODO TODO
numpy TODO =) TODO
pylab TODO =) TODO
pkg_builder TODO =) TODO
openalea_meta TODO =) TODO
VPlants
PlantGL TODO TODO TODO
WeberPenn TODO TODO TODO
aml TODO TODO TODO
aml2py TODO TODO TODO
amlobj TODO TODO TODO
cmechanics TODO TODO TODO
container TODO TODO TODO
cphysics TODO TODO TODO
fractalysis TODO TODO TODO
lpy TODO TODO TODO
mechanics TODO TODO TODO
mtg TODO TODO TODO
newmtg TODO TODO TODO
pglviewer TODO TODO TODO
phyllotaxis_analysis TODO TODO TODO
physics TODO TODO TODO
sequence_analysis TODO TODO TODO
stat_tool TODO TODO TODO
svgdraw TODO TODO TODO
tissue TODO TODO TODO
tool TODO TODO TODO
tree TODO TODO TODO
tree_matching TODO TODO TODO
tree_matching2 TODO TODO TODO
tree_statistic TODO TODO TODO
vplants_dev TODO TODO TODO
vplants_meta TODO TODO TODO
OpenaleaPkgs
caribu TODO TODO TODO
graphtal TODO TODO TODO
adel TODO TODO TODO
topvine TODO TODO TODO

1) Has the branch been done?

2) Is the branch up-to-date? For the 1.0 release, Openalea trunk was branched as a whole. VPlants was branched per package to release. Later on, do the same for Openalea as this makes it MUCH easier to track changes and merges.

  • Green : Package is frozen and ready for release
  • Yellow : Package was recently merged (< 2 weeks) but not frozen
  • Red : Last merge was too long ago.

3) Are the eggs uploaded? python multisetup.pt bdist_egg and python multisetup egg_upload

4) Are the sources uploaded? python multisetup.pt sdist and python multisetup ????

5) Is the documentation complete ?

  • Green : documentation is useful and rich
  • Yellow : documentation is minimalistic but helpful
  • Red : documentation is poor

6) Is the documentation on the server ?

7) Is the package listed in the multisetup.py toplevel script? This is important as it is the top level tool to build and distribute the packages.

TBD

  • Automate the release using CI / VirtualBox / osc:
    • CI: add nightly build binary version
    • VirtualBox:
      • external developers can build eggs for their OS
 
documentation/release_status_1.0b1.txt · Last modified: 2012/03/21 17:31 by user   Back to top
INRIA   INRA     CIRAD     AGROPOLIS
INRIA GForge RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki