On Tue, Feb 5, 2013 at 2:09 PM, Alec Warner <anta...@google.com> wrote: > On Tue, Feb 5, 2013 at 10:07 AM, John Moser <john.r.mo...@gmail.com> wrote: >> I have no sympathy for the use case of running your Puppetmaster as >> LTS and expecting the next five years of Ubuntu releases to hold back >> updating Puppet just so you can mix and match LTS server with >> latest-release clients. Among other things, this would cause an issue >> where overlapping LTS (i.e. 3 years between) would require the new LTS >> stay on the old Puppet, which means that Puppet never gets upgraded >> since there is always an in-life LTS holding back Puppet for all >> further releases when a new LTS comes out. > > I don't think any sane customers expect this (and I do not.) Letter > updates (P -> Q, Q -> R) are when I expect changes (and pain!) But > that is why we are on a release based OS and not a rolling release > like Arch ;) >
Oh good, then we're on the same page. On a related note, Puppet 3.1 came out ... yesterday. So next debate: 3.0.2 or 3.1 into Debian experimental? (I've been trying to get it brought in) 3.1 did not include https://projects.puppetlabs.com/issues/16856 or I would be lobbying heavily for 3.1 into Experimental and then directly into Ubuntu. As is, there are good arguments for sticking to 3.0.2 in this scenario (notably: stuff was deprecated in 3.0; it is GONE in 3.1, and now Ubuntu/Debian have to make a jump since next Stable will be 2.7 for Debian and the last was 2.7 for Ubuntu. The 2.7 -> 3.1 jump is nasty). Alec, I'm sure you can appreciate the implications, as well as the challenging difficulties now faced due to failure to keep up with a fast moving target. If it's that important, we may need to just throw down 3.0 and 3.1 and meta-packages for a while here. This is all kinds of badness, too: 3.0 is dead; 3.0.2 is the last and there will be no more updates to the branch (think Apple Quicktime, you know the drill), so we definitely don't want to support Puppet 3 for an extended time because no bugfixes. TBH, for Puppet in general, your task is to keep up; like Pacemaker, Corosync, and Heartbeat, Puppet is racing towards advancement and things are rapidly changing. You should see the mess that is Pacemaker/Corosync, trying with RHEL5 and RHEL6 and SuSE and Debian gets you many different procedures and different configurations required. It's now somewhat stabilized, and has grown into something awesome. Puppet is doing that right now and pain will come. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
