Juju 1.17.0 on trusty means no production work
I am dismayed to see that juju 1.17.0 was put into trusty. We know it is not backward compatible. Since the juju stable PPA only contains backports from trusty, there is no juju stable package for me to install through an archive. A sad day for me to respond to a production-level issue with production/stable jujus. I am happy to run trusty and test the new packaging of stable software. Juju 1.17.0 is not stable, it is not compatible with 1.16.x, and was not given a choice, nor informed that I could be risking someone's assets. I don't think ubuntu devel series should be getting devel juju, at least not until we have full devel to stable compatibility testing. If we put juju into trusty because everyone on trusty myst test juju, then we need to offer out testers an obvious and safe path to remain stable, I don't think pinning juju packages is obvious or right because I do want stable packages. We can offer stable and unstable versions in trusty. For the time being, I am going to create a stable trusty juju and place it in the stable ppa so that some people have a choice to respond to production situations. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju 1.17.0 on trusty means no production work
James/Scott/Pat? Long term goal is to sync with whatever is latest stable before release, no? Sent from my iPhone > On Jan 23, 2014, at 2:53 PM, Curtis Hovey-Canonical > wrote: > > I am dismayed to see that juju 1.17.0 was put into trusty. We know it > is not backward compatible. Since the juju stable PPA only contains > backports from trusty, there is no juju stable package for me to > install through an archive. > > A sad day for me to respond to a production-level issue with > production/stable jujus. > > I am happy to run trusty and test the new packaging of stable > software. Juju 1.17.0 is not stable, it is not compatible with 1.16.x, > and was not given a choice, nor informed that I could be risking > someone's assets. I don't think ubuntu devel series should be getting > devel juju, at least not until we have full devel to stable > compatibility testing. > > If we put juju into trusty because everyone on trusty myst test juju, > then we need to offer out testers an obvious and safe path to remain > stable, I don't think pinning juju packages is obvious or right > because I do want stable packages. We can offer stable and unstable > versions in trusty. > > For the time being, I am going to create a stable trusty juju and > place it in the stable ppa so that some people have a choice to > respond to production situations. > > -- > Curtis Hovey > Canonical Cloud Development and Operations > http://launchpad.net/~sinzui > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Juju 1.17.0 on trusty means no production work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Curtis On 23/01/14 19:53, Curtis Hovey-Canonical wrote: [...] > I am happy to run trusty and test the new packaging of stable > software. Juju 1.17.0 is not stable, it is not compatible with > 1.16.x, and was not given a choice, nor informed that I could be > risking someone's assets. I don't think ubuntu devel series should > be getting devel juju, at least not until we have full devel to > stable compatibility testing. FWIW I did raise this at the cross-team meeting on the 16th of January so people should have been aware that this work was happening; the rationale for the 1.17.0 release upload was: 1) its the first release to support gccgo - and we need to be testing with juju built using this toolchain. 2) its closer to the stable release we will be releasing with. We really need to kickoff the Main Inclusion Review process now if juju is to be in main for 14.04; asking the MIR team to review the previous stable release of juju seems pretty pointless when its going to be using a different toolchain and work in different ways for release. [...] > For the time being, I am going to create a stable trusty juju and > place it in the stable ppa so that some people have a choice to > respond to production situations. If the situation is that bad, then I can revert the 1.17.0 upload to trusty and switch back to 1.16.5. Regards James - -- James Page Ubuntu and Debian Developer james.p...@ubuntu.com jamesp...@debian.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJS4iKaAAoJEL/srsug59jDnfkP/0NYpEGX9AHF3LRheMTquZo3 8CmO75HUfobucNLEctm0nnUI95krzxIlQBUlbny4qPwKN3mDDkv7Efpnl8upV4oi NJUs1JKgRmyYxKwHJC7i2C+NnQ+4M1G3ChcaIxZjzHINJk9gZy1FG1e99i3X18Fs lgp0rjQmqlt9eJ/q/HBRrezfosQXtEgSnM/Yst6p/eKMyr9hiXI+Y4NiZhlJB835 ylqy5n2tboPxkI7UUqhTY26XKrME9VV7UBZlhL1nNtIdWlzvUi8pYvsBS+n1+IiM Bz0Ue9XjbNjWxOZUFDzpa9wmxb+odmZe57C86/M2PNQ7bixiCH4IeVu7h9v/Zgir JOThndTRvfnrpWL/6MfSnx5tIuyI8zxZb9GYEJpo56290YOlNiO6l8aeX/5umUWu fMHiyzVSWPrArNNaxMAfAaNAuahTJrLFvyMqi0GCtfk3jeCx7CD+XoSRxanZM6Ln fOzs8kGK9ChgOs8hqP5b0vQBGMb/a8+dBex9kzFupUrvSgYe40tr6/GKPBA13qfi JfXWAt6nYukdjrHuDr8vTxwC0xWZDIWZsFyHpVpUg01CIlD2WmKOXUKcJoNgb/Mk sL0PMgdPd/hF/riNcRJscKKSf+myGIa9PW1hW3ZWzrdk9JHrVbZVyrqK7QJxfsLg YTWnKF8k75a6QUqa7gwM =jeui -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
