+1 for a warning.. "Warnings are the precursors to education" - me, just now On 07/02/2014 11:55 am, "Marcel Kinard" <cmarc...@gmail.com> wrote:
> +1 to this. > > How about this addition: if the setting isn't explicitly declared in > config.xml, log a warning but still default to exactly where they are now. > > On Feb 5, 2014, at 10:50 AM, Ian Clelland <iclell...@chromium.org> wrote: > > > So this proposal would be: > > - Don't revert the changes made on dev > > - Don't rename the plugin > > - Add a default which places files exactly where they are now > > - Bump the major version > > - Start fixing bugs in the new code. (without being distracted by the > > storage location change) > > - Start blogging about the issue with storage locations, and encourage > > people to change (but don't force them to do anything yet) > > - In a year, or when we feel that a sufficient mass of developers have > > gotten the message, broadcast that we're removing the default. (or > changing > > it, if we're very confident in our plugin upgrade paths) > > - Some months after that, make the change. (and hopefully not be > > distracted by bugs in the underlying plugin code) Bump the major version > > again. > >
