Community
Participate
Working Groups
We'll use this bug to track the MoDisco 0.11.0 release for Kepler. Hugo submitted the IP Log; I have reviewed it and forwarded to the IP Team for their review. Note that, per bug 393682, mid-level modeling projects are being terminated; MoDisco needs to move from modeling.mdt.modisco to modeling.modisco. We need to enumerate the required changes so that webmaster can effect them. * Change project id from modeling.mdt.modisco to modeling.modisco * Update bugzilla product from "MDT.MoDisco" to "MoDisco" * No changes required for the SVN repository (consider migrating to Git) * Project website, and downloads are already in the root; no change is required What have I missed?
Hello, The root download URL is http://download.eclipse.org/modeling/mdt/modisco/. I assume this have to be changed. Regards, Grégoire
I noticed that you've already created an release record for MoDisco 0.12.0. Is it almost time for MoDisco to graduate?
The IPZilla component also has to be changed from modeling.mdt.modisco to modeling.modisco (and related CQs migrated accordingly). Concerning the graduation of MoDisco, this is part of the future plans but we would first like to start from a clean Git repository (migration to be performed during the months after the Kepler release). Hugo
To my point of view, we have to finish the migration to EMF Facet before to graduate. The MoDisco browser still use the old version of the facet framework. I would like to remove the old implementation of the facet and switch to EMF Facet before to graduate. Furthermore, I assume that EMF Facet has to graduate before MoDisco because MoDisco depends of EMF Facet. Regards, Grégoire
+1 This makes sense to me Grégoire. Hugo
Created attachment 231656 [details] Approved IP Log
The Docuware, including the approved IP Log and project's short description, is available from http://projects.eclipse.org/projects/modeling.mdt.modisco/reviews/0.11.0-release-review The Modeling PMC validation is available from http://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg02872.html
I declare this review successful! Please continue with your release. Please assemble a list of action items to complete the move of this project. There are a few projects that need to move, so let's wait until we have all/most of them ready to go before we copy the webmaster and ask him to effect the changes all at once.
Wayne, As asked, here is a first version of the lists of actions concerning MoDisco: * Update bugzilla product from " MDT.MoDisco " to " MoDisco " (and migrate corresponding bugs accordingly) * Update ipzilla component from " modeling.mdt.modisco" to " modeling.modisco" (and migrate corresponding CQs accordingly) * No changes required for the SVN repository (migration to Git to be performed during next year) * No changes required for the project website (already independent) * Change project id from modeling.mdt.modisco to modeling.modisco * Change root download URL from http://download.eclipse.org/modeling/mdt/modisco/ to http://download.eclipse.org/modeling/modisco/ Concerning the two last items (and more particularly the last one), as raised during ongoing discussions on the Modeling PMC list, they could potentially provoke some issues: maybe the treatment of these specific items could be postponed after the official Kepler release and integrated only for Kepler SR1?
(In reply to comment #9) > Concerning the two last items (and more particularly the last one), as raised > during ongoing discussions on the Modeling PMC list, they could potentially > provoke some issues: maybe the treatment of these specific items could be > postponed after the official Kepler release and integrated only for Kepler SR1? Are these still an issue in your mind. FWIW, I have no problem with the project continuing to use the current download directory. Perhaps you might consider asking the webmaster to create the new directory and start putting your new builds there. Over time, the content of the old directory will become stale and naturally disappear as it is archived.
(In reply to comment #10) > > Are these still an issue in your mind. > > FWIW, I have no problem with the project continuing to use the current > download directory. Perhaps you might consider asking the webmaster to > create the new directory and start putting your new builds there. Over time, > the content of the old directory will become stale and naturally disappear > as it is archived. Hello Wayne, After internal discussions, we have agreed that these are not issues anymore since the Kepler release is now done. Thus, all the actions mentioned in comment #9 can be performed as part of the MDT project termination. Hugo
We dropped this ball. Let's pick it up again post-Luna and make it happen.
Housekeeping
