Hello,
On Tue, Sep 30, 2014 at 3:12 PM, José Antonio Rey wrote:
> Hey Jorge,
>
> From working with you in the past I can say you are a very dedicated member
> of the team, and willing to give a hand.
>
> No objections on my side, +1!
[ ...]
>>
Thank you to all ~charmers for your consideration on
juju can save minutes per machine (especially against release images) if we
turn off upgrades by default. At the moment in juju 1.21 (dev) there's a
setting os-enable-upgrade: false that will do just that (apt-get update
but not upgrade) but thats not by default. i wanted to raise the question
of
On Wed, Oct 1, 2014 at 3:26 PM, Kapil Thangavelu
wrote:
> juju can save minutes per machine (especially against release images) if we
> turn off upgrades by default.
There are some updates coming to how we build cloud images that might
be relevant to this discussion:
http://blog.utlemming.org/201
I believe that, as Jorge mentioned, most users do value having everything
up to date by default, specially when they may go directly to production
environments. Devs may also want to use this switch, as it will save time
during the deployment for testing the charms they have developed.
I believe t
So there is the question of what is the "user experience", and people
trying out Juju and it seems slow. Though if it is slow, doesn't that mean
that images are out of date?
I just bootstrapped a fresh Ubuntu from Amazon's web interface today, and I
noticed that apt-get upgrade on there installed
