On Tue, Feb 12, 2013 at 4:11 AM, Jürgen Schmidt <jogischm...@gmail.com> wrote: > On 2/12/13 12:41 AM, Rob Weir wrote: >> On Mon, Feb 11, 2013 at 5:37 PM, Hagar Delest <hagar.del...@laposte.net> >> wrote: >>> Le 11/02/2013 22:46, Rob Weir a écrit : >>>> >>>> My impression was that even if we made no changes, from the user's >>>> perspective, they would lose all extensions. This is due to the >>>> change in base directory for the profile. So all extensions would be >>>> lost and need to be reinstalled. So there will be no doubt in the >>>> user's mind, even if they do not read the release notes, that the >>>> extensions are gone. >>>> [...] >>>> >>>> Again, my impression is that users will lose their extensions and need >>>> to reinstall them, even if we do not make any API changes. >>>> [...] >>>> >>>> I think a "clean break" with the past profile helps us avoid the >>>> current generation of crash issues. We get to start clean rather than >>>> deal with the many upgrade paths: >>> >>> >>> No real problem with reinstalling extensions after a major upgrade, I've >>> done that too. >>> But there is a difference between the mere inconvenience of reinstalling >>> extensions and losing them completely (waiting that someone dare update >>> them). >>> >> >> Is that what we're really facing? Are you saying that extension >> author will not update their extensions if they become incompatible? >> Is that what we think? >> >> I agree that this would be a bad situation. But is it the likely >> situation we would face? The authors of the top extensions would not >> update? > > If that is the case than we can stop to talk about extensions at all. I > would not spent any further minute to make the life of extension > developers easier. >
I don't know. I was asking a question. But I think this is an important question: Why would an extension author not update their extension for AOO 4.0? Some hypothetical answers: 1) The extension is unmaintained 2) The author cannot be located or we have no way to notify them of changes 3) It is not clear to the author what technical changes are needed 4) There is not sufficient calendar time for the extension author to make the needed changes before we release, or the work required is too much for the author to fit into his schedule 5) The author attempts changes but they don't work or they introduce new problems 6) The results of not making the changes is not clear, so the author mistakenly thinks they are optional changes 7) Author has technical or account issues with the extensions website and is unable to upload a new version, and does not know where to get help. These are all possible concerns, but I think most of them can be managed with good communications and advance notice. There is also the possibility of: 8) Inconvenience -- it is natural for anyone to complain about needing to do additional work where they don't see the advantage. So it is natural that we will expect complaints, followed in the end by conformance with the required changes. What is totally unclear to me is whether we are facing #8 only, or whether we have any of the other concerns. One option for #8 is to add a nice new feature or capability to the API so extension author will *want* to update. -Rob > Juergen
