Bug 566726

Summary:	Remove ProxyManager#checkMigrated introduced in 2010 via Bug 242057
Product:	[Eclipse Project] Platform	Reporter:	Lars Vogel <Lars.Vogel>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	Lars.Vogel, rolf.theunissen
Version:	4.17
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Lars Vogel

2020-09-07 06:51:37 EDT

10 years later, I think it should be fine to remove the proxy manager migration.

Comment 1 Lars Vogel

2020-09-07 06:51:50 EDT

Rolf, WDYT?

Comment 2 Rolf Theunissen

2020-09-11 10:55:21 EDT

Given that we already made changes that do not migrate older workspaces, these migrations can be removed as well.

Should a policy be created and communicated with the user (e.g. in the release notes) that states how 'old' workspaces can be to be opened in a newer version?

(B.t.w. in notice that you open all your bugs against version 4.14, is that a deliberate choice?)

Comment 3 Lars Vogel

2020-09-11 10:57:07 EDT

(In reply to Rolf Theunissen from comment #2)
> Given that we already made changes that do not migrate older workspaces,
> these migrations can be removed as well.

Great. Do you want to take this one too?

> Should a policy be created and communicated with the user (e.g. in the
> release notes) that states how 'old' workspaces can be to be opened in a
> newer version?

I think the last release N&N is fine.

> (B.t.w. in notice that you open all your bugs against version 4.14, is that
> a deliberate choice?)

I guess that is a browser cookie.

Comment 4 Rolf Theunissen

2020-09-11 11:02:57 EDT

(In reply to Lars Vogel from comment #3)
> (In reply to Rolf Theunissen from comment #2)
> > Given that we already made changes that do not migrate older workspaces,
> > these migrations can be removed as well.
> 
> Great. Do you want to take this one too?

Given my current workload and that I am not really familiar with how preferences are handled, I don't think I can work on this.