<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Change user profile folder for 6.0" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113783#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Change user profile folder for 6.0" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113783">bug 113783</a> from <a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> Michael Meeks</a> <pre>Discarding users' customization as they upgrade seems really unfortunate. The ESC discussed this last week, and are unconvinced by a number change here - we deliberately didn't do this in the past to avoid issues here. Ultimately if a user has not configured some part of the UI, or eg. table-styles in general they should not have a hard-coded configuration for that in their config directory - so, they should see the new changes eg. toolbar re-org. Those who did take the time to configure things as they want them will not be disrupted. There are a load of potential ways to fix and improve this code, and/or to detect a one-off upgrade and allow the user to choose to use the 'new' stuff for whatever areas they configured - but they all involve real coding work, and rather unpleasant testing (AFAIR our unit tests for migration code are/were very poor indeed). So - absent some developer to work on this in the next 10 days - this is unlikely to happen for 6.0 I think.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>