-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-04-29 09:41 AM, Nate Finch wrote: > I think you're missing roger's point.
No, I understand his point, and I think that his extrapolation is incorrect, and I explained how. > 1.18 has some fallback code to support 1.16. However, we don't > support 1.16 anymore. But because that fallback code is a > "feature" in 1.18, we have to support it in 1.20. But that means > that even when 1.18 is EOL... 1.20 still has the "feature"... and > thus we have to support it in 1.22. And even when 1.20 is EOL... > etc Right, if 1.18 supported it directly. But if 1.18's behaviour was to migrate, rather than support directly, then when Trusty was EOLed, we could assume that everything had been migrated, and drop support for the migration. > Once Trusty EOLs, then I think we would be able to drop > functionality that 1.18 itself used only for migration. > > For example, if juju 1.18 had automatically created .jenvs from > the environments.yaml instead of using environments.yaml directly, > then when Trusty EOLed, we could drop that functionality. > > The other thing is that Juju 2.0 will not have this requirement. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVQOFLAAoJEK84cMOcf+9hgsoIAMFNwJxD2muYhpp2CeD8knLx LDQtoyQoYgHWh3xlJS20uYyjzCLEJg7V3392GOLC6mqhltaMtNcSjTXGakJD2mVj LUHUINfcOQZPm/LLftSfYSgk3MFFlvYtU1es6lzSCgBTFJ0U2mZ1wEn/dXnWlotm XUuR8QVT4PCUMivjEjLefevY+bpetRWB7AlspOOuyfJxO+/4O2h4iBnHKeP8yUlV HJnQWskdg7Vi7vIaPGONYbcIg3uaBsWFPpc2AEEMWIsmqlf3NyXtgHmK/EHMdG0W w+GOTzvch8XCZ6AnzqQbo64W5Hb55al4bmN1jQGm4czTJ2W8E45vBnrAny3Fm88= =NPEr -----END PGP SIGNATURE----- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
