[Bug 1314686] Re: Please add support for utopic
Robie Basak
1314686 at bugs.launchpad.net
Mon May 12 01:39:30 UTC 2014
I'm thinking about any implications for future releases. Are we going to
get this failing on every release, assuming that we won't know the next
release's codename in advance again? If so, this seems bad from a
distribution perspective to me, as the need to SRU fixes to juju-core
may often be the highest just after release, and this will block us (or
at least slow us down while we arrange an exception to the usual
process).
Can I suggest a dep8 test in packaging to fake a "future" codename to
make sure that juju can work in that circumstance (at least for the
local provider)? I'll happily write this given some guidance - how does
juju pick up the current release name? Do I just need to mangle /etc
/lsb-release so that "lsb_release" gives me something different?
If we do expect this to fail in a similar way every release, should I
file a separate bug to track this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1314686
Title:
Please add support for utopic
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1314686/+subscriptions
More information about the Ubuntu-server-bugs
mailing list