Must to do things at client side before executing migration from RTC 3.0.1.x to 4.0.6
Hi
Is there any thing which must be (not "better to be" )done by end users, i.e RTC clients, before executing migration from RTC 3.0.1.x to 4.0.6?
For example, follwing things.
- Unlock all locked files
- Check in / Deliver all change sets
- copy(back up) ".metadata" of their eclipse local workspaces
I could not find above information in following InfoCenter/Wiki. My clients use Scource Management, Workitem Management, and Build Management feature of RTC.
My understanding that It is enough for them to back up files in their local workspaces.
In case of ClearCase, there are some thins must be done by end users. But RTC does not have such a things?
Thank you in advance.
Natsumi
Accepted answer
Let us know if that helps.
Comments
Hi,
Thank you for your answer. Could you tell me why you recommend to clear browser cache?
If you use web client, html and js code is changing through versions. It is important to use the latest code, not one cached by web browser. We had couple of issues with that especially when using proxy server.
1 vote