On 5 June 2013 13:36, Rob Weir <robw...@apache.org> wrote:

> I'm a little confused by recent threads on the upgrade logic.  But I'd
> like to ensure that this area is adequately tested and that we
> understand how it behaves so we can better support users.  So here are
> some questions to flesh out the way it will work with AOO 4.0.
>
> 1) When an AOO 3.4.1 user profile customizations configured, what
> happens when they install AOO 4.0?
>
> 2) If anything is not migrated are users given any warning, so this is
> not a surprise?  (Maybe we need something in the Release Notes at
> least?)
>
> 3) Does this include custom spell checking word list?  Old Extensions?
>
> 4) What happens to the old AOO 3.4.1 install directories?  Is it
> removed?  Does that include extensions?  other files?  Is it totally
> clean?
>
> 5) If extensions are not migrated, is there anything that helps the
> user to know what extensions they need to reinstall?  If not
> automated, maybe we need something in the Release Notes to explain how
> a user can make this list *before* they install AOO 4.0?
>
> 6) Does any of the above change if they are upgrading from AOO 3.4.0
> or OOo 3.3.0 or earlier to AOO 4.0?
>
> 7) Once AOO 4.0 is installed, what happens if a user tries to install
> an extension that has not updated addons.xcu?  Is there an obvious
> error message, directing the user to contact the extension developers?
>
> 8) Same for incompatible C++ extensions.  Is the user given a
> meaningful message that directs them to the extension author?  Or will
> they be confused and end up asking us for help?
>
> 9) Is there any easy way users can tell which extensions on the
> Repository are compatible with AOO 4.0?
>
> 10) Are there any test extensions that QA can use to test the positive
> and negative cases of  #7 and #8 above?
>
> 11) Are there any other edge cases we need to think about?  Maybe
> future-proofing?  What happens to a future incompatible AOO 5.0
> extension when installed on AOO 4.0?
>

Good question, and a good idea to get it all in one thread.

How about downgrading 4.0 -> 3.4.1 when a user e.g. finds out an important
extension does not work in 4.0

rgds
jan I.


>
> I'm happy to update the Release Notes if the developers can clarify
> the expected behaviors here.
>
> Thanks!
>
> -Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Reply via email to