On Mon, May 6, 2013 at 1:25 PM, janI <j...@apache.org> wrote: > On 6 May 2013 18:27, Rob Weir <robw...@apache.org> wrote: > >> What do we need to do to test AOO 4.0 -> AOO 4.1 upgrade scenario? >> > > Do we already have documented procedures for the AOO 3.4.1 -> AOO 4.0 > upgrade ? > (searching in wiki for "4.0 upgrade" gives no result) > > If not I would suggest we make the documentation and test plan for the > 3.4.1 -> 4.0 before thinking about the next upgrade. > > One thing that really needs to be tested is a 3.4.1 danish (example) > installation, upgrade to a 4.0 english installation. At this point in time > I foresee a 4.0 release with less languages than 3.4.1 (with language > respin). The tests should include fallback scenarios for users who want to > stay with their language version. >
Two different things: 1) The upgrade notifications. This is triggered by an XML file we put on our website that the client checks, by default once a week. For example, here is one of the existing update notification files: http://www.openoffice.org/projects/update38/ProductUpdateService/check.Update There is a different base URL for each version, pointing to a file like this that lists the available upgrades for that version. Since the update checking code has changed, we should make sure we have good testing on that, on all platforms. There was also talk of making that update check occur over SSL. That could be done by: A) Getting an SSL certification for *.openoffice.org or for the specific subdomains of interest or B) Moving the update notification files over to openoffice.apache.org, where we can presumably just use the existing Apache certificate However we do it, we need code changes in 4.0 to accommodate this, and testing as well. 2) The actually install of 4.0 over AOO 3.4.1. My impression was that major upgrades like this installed into a new directory and there was no automatic migration of settings. If so the testing side of it would not be difficult. Same for reinstalling 3.4.1 over a 4.0 installation. Different directories, so no conflict. -Rob > +1 to testing the upgrade scenarios. > > rgds > jan I. > > >> >> Is it possible to put an update XML file on the server so we can >> trigger update checks, etc., to verify that this is working? >> >> As we know, we had some update checking crashes in AOO 3.4.1, so we >> really should try to get some test coverage of both positive and >> negative checks. Maybe one locale (English) we say there is an >> update, and in another locale (German) we say there is no update, so >> we can exercise both paths? >> >> Of course, we would then need to remove the test file from the web >> server before we ship. >> >> -Rob >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
