On Tue, Nov 18, 2014 at 11:23 AM, Joshua Hoblitt wrote:
> On 11/18/2014 12:04 PM, Eric Sorenson wrote:
> > 2. To enable #1 but still support OSes that ship with 1.8.7, we're
> > going to be packaging and delivering Puppet 4 an an 'all-in-one' (AIO)
> > package bundled together with
> > - openssl
Hi Josh,
I will plan to attend the PR triage on Wed.
On Thu, Nov 13, 2014 at 11:52 PM, Josh Cooper wrote:
>
>
> On Thu, Nov 13, 2014 at 10:35 AM, Geoffrey Gardella
> wrote:
>
>> Hi Josh!
>> I am with Oracle and have just been assigned to work on Puppet in
>> Solaris. I am just getting oriented,
On 11/18/2014 12:04 PM, Eric Sorenson wrote:
> 2. To enable #1 but still support OSes that ship with 1.8.7, we're
> going to be packaging and delivering Puppet 4 an an 'all-in-one' (AIO)
> package bundled together with
> - openssl
> - ruby
> - augeas
> - ruby-augeas
> - ruby-stomp
> - ruby-s
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
to see exactly what's going in, it might be helpful to have
On Tuesday, November 18, 2014 3:35:25 AM UTC-6, Mike Hendon wrote:
>
>* Please note that some changes in puppet 4 mean that puppet 3 agents
> won’t be able to talk to puppet 4 masters (or vice-versa).
>
> This might cause an issue.
> I would suggest that the puppet RPMs are renamed to someth
* Please note that some changes in puppet 4 mean that puppet 3 agents
won’t be able to talk to puppet 4 masters (or vice-versa).
This might cause an issue.
I would suggest that the puppet RPMs are renamed to something like puppet4
so that unexpected breakages don't occur.
--
You received th
