Hello,
With the release of Facter 1.7.1[1], we'd like to delete the `1.7.x` branch
in
an effort to streamline the contribution process to Facter by using
statically
named branches, `stable` and `master`. Moving forward, any bug fix that
would
have gone into `1.7.x`, should instead be targeted a
On Mon, Nov 5, 2012 at 4:56 PM, Erik Dalén wrote:
> Any plan of implementing caching for 1.7?
>
> "Starting with Facter 1.7.0, you can now specify that the contents of a
> fact’s “setcode” block should be cached for faster retrieval."
>
> Quote from http://docs.puppetlabs.com/guides/custom_facts.h
On Mon, Nov 5, 2012 at 7:10 PM, Tim Sharpe wrote:
> I would consider stripping whitespace to be a bugfix rather than a
> backwards incompatible change.
>
>
Unfortunately a lot of bugfixes end up being backwards incompatible. One
that I'm on the fence about for 1.7.0 is the fix for #14827. It is a
I would consider stripping whitespace to be a bugfix rather than a backwards
incompatible change.
On 03/11/2012, at 7:47 AM, Andy Parker wrote:
> Right now facter has a branch called 2.x, which was supposed to be getting
> ready for a 2.0.0 release of facter. That hasn't happened yet and there
I would really like to see it implemented and have been forced to
reimplement it internally in a few custom facts that take long time too
lookup and seldom change (mostly reading stuff from raid controllers, bios
settings, LOMs etc).
And as it is the only feature afaik that has been promised befor
I worked on getting external facts (
http://projects.puppetlabs.com/issues/2157) implemented, and I wound up
removing the work on caching. Both external facts and caching are pretty
big tasks in and of themselves so I did the work to get external facts into
core and decided to defer caching for som
Erik Dalén wrote:
> Any plan of implementing caching for 1.7?
>
> "Starting with Facter 1.7.0, you can now specify that the contents of a
> fact’s “setcode” block should be cached for faster retrieval."
>
> Quote from http://docs.puppetlabs.com/guides/custom_facts.html
I think the caching ran
Any plan of implementing caching for 1.7?
"Starting with Facter 1.7.0, you can now specify that the contents of a fact’s
“setcode” block should be cached for faster retrieval."
Quote from http://docs.puppetlabs.com/guides/custom_facts.html
--
Erik Dalén
On Friday 2 November 2012 at 16:47,
Right now facter has a branch called 2.x, which was supposed to be getting
ready for a 2.0.0 release of facter. That hasn't happened yet and there are
quite a few changes on the 2.x branch (and master since there are no
differences between the two). I'd really like to see those changes be
released
On Thu, Sep 29, 2011 at 5:21 PM, Ken Barber wrote:
> Hi everyone,
>
> So we've just prepared the branch for Facter 1.7.x and merged up any
> changes that existed in 1.6.x. This means the branch is ready for work
> to accept feature level changes such as API changes or major
> structural changes t
Hi everyone,
So we've just prepared the branch for Facter 1.7.x and merged up any
changes that existed in 1.6.x. This means the branch is ready for work
to accept feature level changes such as API changes or major
structural changes that can be generally categorized as "major". There
are already s
11 matches
Mail list logo
