1.2 Requirements for updating OpenCMISS-Iron dependencies #191
Description
- Determine which libraries need to be updated
| Default Header | Left Align | Right Align | Center Align |
| --- | :-- | --: | :-: |
| Dependency | version controlled | version |
|---|---|---|
| Petsc | yes | |
| Sundails |
- List dependency library versions in a different file in the manage repo. (there might be some information in the build files that have some of this information e.g. which versions work together and which don't).
- Allow the developer to add a list in the iron repo which overrides what is defined in the manage repo. This will allow a developer to test new features against new dependency versions.
How do you roll out version upgrade if you have different users around the worlds?
Potential solutions
Say we will support these specific combinations which would be released. If you require a newer version e.g. which fixes bug, new feature, then let us know and we will add the dependency and create a new feature.
Make list part of the iron repo which requires these dependencies. Then you can tag a particular commit. e.g. bug fix in a library that gets rolled out, but new feature in the iron code that you have written in a different branch. Then if someone checks out the feature then they will know which dependencies to use.
problems
But things are in different repo/and mismatch