Community
Participate
Working Groups
Build Identifier: Hi, The bugs to be moved are: (It contains closed and open bugs in EMF Query2 component till date) 294160 324723 323227 327625 327969 327987 331905 324176 324175 333136 336286 326769 333844 338369 333445 344705 323838 324375 324722 324724 324743 325042 325827 325844 326267 326294 326627 331944 333333 333719 341879 342234 324067 323820 342355 341890 336197 327639 326865 324088 341889 338164 333017 332984 333722 336196 340125 345524 332414 336114 348321 333224 341888 353092 353845 354790 For convenience i have added the same list as excel to this bug. Following sources have to be moved within same repository path i.e: /cvsroot/modeling 1. Move Module (with contents) : org.eclipse.emf/org.eclipse.emf.query/org.eclipse.emf.query2/ to have final path: org.eclipse.emf/org.eclipse.emf.query2 2. Move Module (with contents) : org.eclipse.emf/org.eclipse.emf.query/org.eclipse.emf.query2.releng/ to have final path: org.eclipse.emf/org.eclipse.emf.query2.releng 3. Delete: org.eclipse.emf/org.eclipse.emf.query/prototypes 4. Delete: org.eclipse.emf/org.eclipse.emf.query/tests/org.eclipse.emf.query2.test 5. Delete: org.eclipse.emf/org.eclipse.emf.query/tests/org.eclipse.emf.query2.librarytest Regards, Ashwani Kr Sharma Reproducible: Always Steps to Reproduce: ..
Created attachment 201804 [details] List of Bugs to be moved
We will also need a list of CQs that need to be moved within Ipzilla (if any). Please note if the project you are moving out of still requires the approved CQ, the new project will need to raise a piggyback CQ for the package instead. This applies to EPL CQs as well. Thanks, Sharon
(In reply to comment #2) > We will also need a list of CQs that need to be moved within Ipzilla (if any). > Please note if the project you are moving out of still requires the approved > CQ, the new project will need to raise a piggyback CQ for the package instead. > This applies to EPL CQs as well. > Thanks, > Sharon Hi Sharon The only CQ number is 3358 ,its about the LPG java runtime. Please let me know if you need any further details. cheers, Saurav
I have just a couple of questions: 1) Are you planning to re-use any of the EMF mailing lists / newsgroups? 2) Should all of these bugs be re-assigned to the new generic inbox? -M.
(In reply to comment #4) > I have just a couple of questions: > 1) Are you planning to re-use any of the EMF mailing lists / newsgroups? > 2) Should all of these bugs be re-assigned to the new generic inbox? > -M. Answers to the questions below (a) We will use the existing emf-dev@eclipse.org and the EMF sub forum (b) Yes Let us know on any further questions. cheers, Saurav
Ok I think we're done here. I've moved the bugs and CVS and sent out the new project stationary. -M.
(In reply to comment #6) > Ok I think we're done here. > I've moved the bugs and CVS and sent out the new project stationary. > -M. Hi, i still dont see my id sasarkar having the project Query2 under itself in the portal. cheers, Suarav
Sorry about that. It's there now. -M.
(In reply to comment #8) > Sorry about that. It's there now. > -M. Well i can see my name now :)
I've set the project lead (missed that the first time through). I'm going to set the project status to regular (i.e. not incubating) since the project exists as the result of splitting up a regular project. The metadata currently specifies a Hudson URL for downloads. This is fine for nightlies, but not acceptable as a general solution. You should provide a proper downloads page that contains a pointer to Hudson for nightlies and proper links on the download server for milestones/releases. Are we done here?
Hi, For setup, we are done. We are currently migration our project to xtext2.0. Once done we will setup update site in download locations and mention it in the udpatesite url section. Regards, Ashwani Kr Sharma
(In reply to comment #11) > For setup, we are done. So, can we say that the purpose of this bug has been served and we can mark it as FIXED?
(In reply to comment #12) > So, can we say that the purpose of this bug has been served and we can mark it > as FIXED?
