Re: What to do with precise charms?

On 20 February 2016 at 03:47, José Antonio Rey wrote: > Hello, > > In approximately two months, Xenial is going to be released. Once that > happens, we are going to have three supported LTS releases: precise, trusty > and xenial. > > I know that there is some people that have

Re: What to do with precise charms?

The multiple-series-charm support has been added in Juju 2.0 specifically to enable upgrades of services in future. The idea is that a charm supports a window of series, and operators can upgrade the underlying hosts smoothly. We don't have quite all the pieces in place yet but its close. In

Re: What to do with precise charms?

Hello Jose, Thanks for bringing this topic up! You make a good point there are going to be three supported LTS releases available to Juju. I do not think we will ask any maintainer to support all three releases. Currently each charm lives in its own release and I would expect the precise charm

What to do with precise charms?

Hello, In approximately two months, Xenial is going to be released. Once that happens, we are going to have three supported LTS releases: precise, trusty and xenial. I know that there is some people that have both precise and trusty charms. However, if they want to move their charms to

Migration of jenkins-charm to upstream repo

Hi everyone, Just a quick note that the Jenkins charm is now at https://github.com/jenkinsci/jenkins-charm Thanks to the Jenkins folks who worked with us to make this happen! -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at:

Re: charmers + openstack-charmers application

I'm not a Juju Charmer, but I am an OpenStack Charmer and Ryan's contributions have been invaluable. A very big +1 from me. On Fri, Feb 19, 2016 at 8:23 AM, José Antonio Rey wrote: > Hey Ryan, > > I'm glad to see your application! You've definitely made valuable > contributions

Re: charmers + openstack-charmers application

Hey Ryan, I'm glad to see your application! You've definitely made valuable contributions in the past months, and I'm very familiar with all the hard work you've put into the charm ecosystem. I'm more than happy to give you a +1 on my side. Thanks for all the work you do! On 02/19/2016

charmers + openstack-charmers application

Happy Friday, charmers! Please consider my application for membership to ~charmers and an ~openstack-charmers. Over the past two years, I've contributed to each of the 20+ OpenStack charms (and jenkins, ubuntu, mysql, mongodb). While most of my work has been in the field of charm testing, I've

Migration of OpenStack Charm development to OpenStack git/gerrit

Hi All As you may or may not be aware, the OpenStack team have been working towards migration of the development process around the OpenStack charms to the OpenStack project. This means we will be moving away from current the bzr/launchpad workflow to a git/gerrit workflow inline with most other

Re: @when('config.changed')

On 19 February 2016 at 16:32, Merlijn Sebrechts wrote: > I completely agree with you on point two. The semantics I'm trying to get at > for point one are a bit different. Events are information that is relevant > for a single point in time, not until the information

Re: @when('config.changed')

Hi Ben I completely agree with you on point two. The semantics I'm trying to get at for point one are a bit different. Events are information that is relevant for a single point in time, not until the information is processed. *Events can be processed by multiple handlers or by none, and in both