Merging multi-project support to the main branch
This blueprint is to plan the merge of multiproject support to Dorsal.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Harish Narayanan
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
0.7.0
- Started by
- Harish Narayanan
- Completed by
- Harish Narayanan
Whiteboard
HN: In general, I understand the changes and am willing to merge the branches, with some minor tweaking. But first, I would like to do another minor release (to fix some bugs with Fedora support). I have already made these changes, once someone confirms they work, I will make this minor release release.
Here are some of my concerns:
1. Will you, or someone else from your FEM projects be around to maintain your package definitions and such in the future?
2. I would like to set up a separate group on launchpad or wherever to handle support questions for your project. The current Dorsal list handles not only problems pertaining to Dorsal, but also FEniCS installation in general.
RP:
Answering the concerns above:
1. The FEMDK project started on march this year and it is scheduled for 4 years so definitely our team will maintain packages
definitions for FEMDK.
2. This is a good idea. At the moment I am launchpad (and bzr) novice, so all your suggestions are welcome. Additionally we have
our Trac site https:/
However I consider Dorsal an external tool for FEMDK and to keep everything in one place I would maintain it via launchpad/bzr.
HN: I have performed the merge! We will figure out how to separate FEniCS and FEMDK support soon.
