If we're removing goose down from the downgrade procedure, but still requiring support for it, doesn't that just make finding issues with it more difficult since fewer use cases would use that codepath?
Jonathan G On 10/23/18, 10:27 AM, "Dave Neuman" <[email protected]> wrote: >>We still need the ability to do a goose down Rawlin has already stated that we will not be losing this ability. We will just be adding the ability to do a wholesale downgrade of the database.
