The notes from today's triage are posted at:
https://github.com/puppet-community/community-triage/blob/master/core/notes/2014-11-19.md
This time we focused on the oldest PR's against the puppet repo, and we
managed to review all of them, except for Trevor's PR for
https://github.com/puppetlabs/pup
Thats cool a controlled and independent stack with all the dependencies.
Independent of the OS is great. Scl works only on rhel 6 and 7.
Please don't forget rhel 5 packages also. I know it is outdated but it is
still widely used .
And bundled software will need to receive security updates, ex rub
- Original Message -
> From: "Eric Sorenson"
> To: "puppet-dev"
> Sent: Wednesday, November 19, 2014 8:36:40 PM
> Subject: Re: [Puppet-dev] Puppet 4 delivery and upgrades
> On Nov 19, 2014, at 11:20 AM, Trevor Vaughan wrote:
>
>> Hmm...Facter and MCollective not being independently u
Hi Matthaus,
The mcollective plugins installed by separate packages but going into
the same path as an "AIO" sounds a bit like reinventing SCLs.
If mcollective was dependent on a ruby run time from an "AIO" puppet
package, and one tried to upgrade puppet with mco, I'd expect there to
be interesti
I always track the latest version of the Puppet-related projects that I use
that don't have exciting bugs against my code base.
I've had to patch things at random in the past to get what I needed until
PRs could be pushed through and I'd like to keep that ability.
The two that generally come to m
On Nov 19, 2014, at 11:20 AM, Trevor Vaughan wrote:
> Hmm...Facter and MCollective not being independently upgradable isn't super
> exciting.
If any one of the main constituent projects having a release would cause a new
AIO to come out, is that the right cycle?
(Do you currently always tr
Hmm...Facter and MCollective not being independently upgradable isn't super
exciting.
On Wed, Nov 19, 2014 at 6:28 PM, Matthaus Owens
wrote:
> Josh,
> Facter and mcollective will both be part of the AIO. Rubygems is part
> of the ruby stack that will be included in the AIO, so installing gems
>
Josh,
Facter and mcollective will both be part of the AIO. Rubygems is part
of the ruby stack that will be included in the AIO, so installing gems
shouldn't change much, you would just need to ensure that the gems are
installed using the AIO gem binary. Facter will no longer be
independently upgrad
On 11/18/2014 12:04 PM, Eric Sorenson wrote:
> 3. The AIO packages will have a filesystem layout that installs the
> programs into /opt/puppetlabs/agent and the configs into
> /etc/puppetlabs/agent ; the packages will be a different basename than
> puppet ('puppet-agent') so won't install automatic
On 11/18/2014 06:11 PM, Michael Stahnke wrote:
>
> On EL6.x, why not use a new SCL? Or even install into the existing
> ruby193 SCL?
>
>
> Part of the goal here is to have control of the ruby version. The SCL
> offers one version of Ruby 1.9.3, Ubuntu offers another in their
> distribution
The Puppet/Facter/Hiera PR triage will be starting in 30 minutes at
http://links.puppetlabs.com/pr-triage
Josh
--
Josh Cooper
Developer, Puppet Labs
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *
http://2015.puppetconf.com.
*Register early to save 40%!*
--
You received this
The merge of beaker PR 536 (https://github.com/puppetlabs/beaker/pull/536)
will end beaker's support of Ruby 1.8. The change will be effective with
the planned release of beaker 2.0 in the next two weeks.
For most beaker users this will have no effect on their daily workflow.
For those who ha
Erik,
The plan is to deliver the AIO package to not just platforms with
older rubies, but to all of the deb/rpm platforms we package for
currently.
On Wed, Nov 19, 2014 at 6:02 AM, Erik Dalén wrote:
>
>
> On Tue Nov 18 2014 at 8:04:13 PM Eric Sorenson
> wrote:
>>
>> Hi all, as some of you have n
On Tue Nov 18 2014 at 8:04:13 PM Eric Sorenson
wrote:
> Hi all, as some of you have noticed, our target date in JIRA for Puppet 4
> is not too far off now. (We just moved it out from early December to early
> January based on the remaining must-have workflow). While you can poke
> through tickets
Yay!
On Tuesday, November 18, 2014 7:11:03 PM UTC-6, Michael Stanhke wrote:
>
>
>
> We'll be picking one Ruby (2.1.z), and using that everywhere for a
> consistent stack.
>
>>
>>
>>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To u
I wanted to let everyone know about some upcoming events where we need
contributions from the Puppet community.
Do you contribute to Puppet core projects, Forge modules or other
Puppet community projects? If so, you should join us in Ghent, Belgium
on February 4 for the 3rd Puppet Contributor Summ
16 matches
Mail list logo
