Community
Participate
Working Groups
We'll use this bug to track the CDO 4.2 release for Kepler. Eike 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; CDO needs to move from modeling.emf to the root (modeling.cdo). We need to enumerate the required changes so that webmaster can effect them. * Change project id to modeling.cdo * Create a distinct Bugzilla product for CDO and move existing categories (EMF/cdo.*) and bugs * No changes required for the Git repositories * Project website, and downloads do not need to be changed What have I missed?
Created attachment 231647 [details] Approved IP Log
Created attachment 231879 [details] Review documentation
Created attachment 231980 [details] Project Plan for CDO 4.2 Hi Wayne, I've locally updated my plan.xml and associated all related bugzillas. Unfortunately I can't seem to push to Git through the EclipseCon Wifi. I've attached the plan.xml so that you can store it somewhere and point the project plan renderer to it. I know you know how toso it :P Sorry for the inconvenience! Please let me know if you get into trouble...
Comment on attachment 231980 [details] Project Plan for CDO 4.2 Ignore my latest comment! I was able to push now. The project plan is available here: http://www.eclipse.org/projects/project-plan.php?planurl=/cdo/project-info/plan.xml
It looks like CDO is good-to-go for the Kepler review.
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.
I peeked at your comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=408271#c27 and assembled a similar list of action items: * Change the project id from "modeling.emf.cdo" to "modeling.cdo" * Create the Bugzilla product "Modeling.CDO" * Move the following Bugzilla *components* from "Modeling.EMF" to the new "Modeling.CDO" product: cdo.core cdo.dawn cdo.db cdo.docs cdo.hibernate cdo.legacy cdo.net4j cdo.net4j.db cdo.net4j.ui cdo.objy cdo.releng cdo.ui * Rename the new components under the "Modeling.CDO" product: cdo.core -> Core cdo.dawn -> Dawn cdo.db -> DB cdo.docs -> Docs cdo.hibernate -> Hibernate cdo.legacy -> Legacy cdo.net4j -> Net4j cdo.net4j.db -> Net4jDB cdo.net4j.ui -> Net4jUI cdo.objy -> Objectivity cdo.releng -> Releng cdo.ui -> UI * There will be changes/moves under downloads/ but too many of our scripts are impacted by such a move. I prefer to do it quite a while after the release to avoid problems with the downloads page.
(In reply to comment #7) > * There will be changes/moves under downloads/ but too many of our scripts are > impacted by such a move. I prefer to do it quite a while after the release to > avoid problems with the downloads page. I have no problem with the moved project keeping the current download directory. Perhaps we can create a new download directory that you can start using at your leisure. At some point in the future, after its content has been archived, the current directory can be removed.
Are we ready to move on this move? Or should I declare victory on the release, close this bug, and leave it between you and the PMC to sort out the move required by Bug 393682?
Hi Wayne, sorry that I didn't come back to you earlier. You know I'm totally absorbed by Oomph right now ;-) In CDO we plan to split our gigantic Git repo into smaller parts. With the new Oomph version I want to create smaller modules for the new CDO "sub projects". That will lead me to new builds (Tycho then) and a new promotion system. That will all impact where the downloads will be available and I really don't want to change anything before these huge changes are started. That's all on my radar, so please feel free to resolve this bug.
Housekeeping.
