Next OpenAlea release 2025

[thomasarsouze]

Discussion space related to the next release (spring 2023) of OpenAlea packages.

[thomasarsouze]

Following the meeting of feb 6th 2023, we target a new release of openalea for FSPM meeting 2023, late march 2023:

• include visualea
• Identify the packages to be released
• target python 3.9 to 3.12
• unify namespace
• all packages to be released in openalea3 repo in anaconda
• make sure all packages have tests
• unify minimum GH-actions for all packages with a call to an action in a repo
• update openalea.rtfd.io matrix of released packages with a minimal jupyter notebook
• if possible make sure to have appropriate documentation of the package

@christian34 @pradal @baugetfa @fredboudon (feel free to add other users)

[pradal]

Release

• core
• grapheditor
• oalab
• stdlib
• visualea

[pradal]

@pellem : Retrieve all these packages plus
https://github.com/openalea/openalea-components

Build a local repo : mamba create -n dev -c openalea3 -c conda-forge openalea.deploy

Clone each repository and install in dev : python setup.py develop

[pellem]

1. Core

• Setup.py : OK
• Tests written : OK
• Tests passed : NOK

2. Grapheditor

• Setup.py : OK
• Tests written : NOK
• Tests passed : NOK

3. Oalab

• Setup.py : OK
• Tests written : OK
• Tests passed : NOK

4. Stdlib

• Setup.py : OK
• Tests written : OK
• Tests passed : OK

5. Visualea

• Setup.py : OK
• Tests written : OK but not exhaustive
• Tests passed : NOK

[pradal]

OpenAlea core (low priority)

• openalea-comp / PyLab
• openalea-comp / NumPy
• openalea-comp /...

OpenAlea Packages : 1st layer (high priority)

• mtg
• plantgl
• lpy
• StructureAnalysis (large work to do)

OpenAlea Packages : 2nd layer

• hydroroot
• hydroshoot
• Phenomenal
• strawberry
• RSML

OpenAlea Packages : Work to do on packaging

• caribu
• PyRATP
• [?] Adel (refactoring)
• EpyMix
• WheatFSPM

[pradal]

Define what is needed for releasing a package

• Documentation
• Tutorial Notebook
• Tutorial VisuAlea
• Tests
• other?

[pradal]

@baugetfa : We can start the new release from here

[baugetfa]

@pradal: I was wondering if it would not be more clean to start a new discussion because this one is 2 years old. Otherwise let's start it from here.

[pradal]

You can of course create a new discussion.
But I have removed the old messages.

I have also updated the project. But we have to manage it differently.
If you can look at it on how to work with projects it would be nice.

I think I have use the project as a discussion.

Perhaps, an idea: create issues per package with setup, meta, test doc.
And assign it to the release project?

@thomasarsouze ?

[baugetfa]

Fair enough, that is fine for me. I'll have a look to the project things. Indeed, we should not make duplication between discussion and project, as for example the pkgs list above and the "conda packaging" in projects.

[thomasarsouze]

Agree that we need to learn how to better work with projects, and that we should not define things to do in the Discussion, but rather only reference the project / tickets / issues / todos / etc... here.

Maybe first define a list of packages (done by @pradal I think) and TODO list of things to be done for each package release, and then we can open the issues for each package.

Later, a TODO list for OpenAlea as a whole (rtfd website, gallery website, etc...)

[pradal]

Yes. We can copy the list from the project to a discussion.
Then each one can create issues in each package, and then associate the issues to a project.

[baugetfa]

It is not so convenient in fact, but we will do with it in fact. For example, every issue that can be followed as to be associated to a given repository. That is logical, but we cannot have a "general issue", a "meta issue", unless keeping the item as draft like this one I modified to set a todo list per pkg todo pkg.
Then we can imagine to start for each pkg an issue called release-reviewing that we link to the project, with a status in progress.
At the pull request, the status would change to Review, and when merge to Done.

[baugetfa]

Question:

I started this review processing with hydroroot. I do it on a branch in my fork. But may be it would be more relevant/easy to make this release review from a branch on the Openalea repository ?

[pradal]

Yes. When we are few to work on the same package, I recommend to have a share branch where we can both commit

[pradal]

And on the project, for each issue, we can associate the issue to the project

[pradal]

The release 2025 has been pubblished