Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334185

Summary: The TM project has moved to Tools, please update our Indigo contribution
Product: Community Reporter: Martin Oberhuber <mober.at+eclipse>
Component: Cross-ProjectAssignee: David Williams <david_williams>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: david_williams
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 330336    

Description Martin Oberhuber CLA 2011-01-12 19:50:45 EST
The TM project has completed its move to the Tools toplevel project. Therefore, our Indigo contribution should be renamed:

  dsdp-tm.b3aggrcon    -->    tm.b3aggrcon

From a brief look, it seemed that there's more involved than just renaming the file (there's a couple References in the Model), so I'd appreciate if somebody who intimately knows the model could do that.

Our project ID also changed from "dsdp.tm" to "tools.tm". Will I need to make any change to the Portal Metadata to ensure we remain listed by the Simultaneous Release Tracker?

Anything else I'm missing?
Comment 1 David Williams CLA 2011-01-12 22:36:14 EST
Done. I simply copy/pasted dsdp-tm.b3aggrcon to tm.b3aggrcon and then did a global replace ... only indigo.b3aggr was effected ... and then removed dsdp-tm.b3aggrcon. So there will be no cvs history for new file. 

An indigo build/aggregation is in progress ... but expect things to be fine from my local workspace verification. 

The metadata tracker for Indigo seems to be tracking tm correctly ... but appears you'll have to re-fill-out some data where other's data was carried over from last year. 

Anything to do for Helios? 

Anything to do for 
dsdp-mjt.b3aggrcon
dsdp-sequoyah.b3aggrcon

Thanks,
Comment 2 Martin Oberhuber CLA 2011-01-14 13:05:04 EST
I have manually re-entered the simultaneous release tracker data:
http://eclipse.org/indigo/planning/SimultaneousReleaseOverview.php?action=project&projectid=tools.tm

Interestingly, the "PMC Executive Info" is not being acknowledged although I entered it. And, the same data appears to be used for both Helios and Indigo which is a bit odd though acceptable:
http://eclipse.org/helios/planning/SimultaneousReleaseOverview.php?action=project&projectid=tools.tm

For Helios SR2, I would NOT like to rename anything ... for now it still pulls from the old frozen DSDP repo location, and I will update the repo location to pull from when we make our Helios SR2 contribution. I think this should be sufficient since changes to the maintenance stream should be minimal.

I don't know what to do about dsdp-sequoyah and dsdp-mtj.

I think for TM, this bug can be closed.
Thanks for your help!
Comment 3 Martin Oberhuber CLA 2011-03-02 04:51:56 EST
Marking resolved for TM.

Sequoyah and MTJ will need to make their case themselves when moving.
Comment 4 Martin Oberhuber CLA 2011-03-02 04:52:51 EST
David, not sure how you want to treat the target milestone? 
I didn't find anything suitable.