It's nice to see a release candidate approach - hopefully it will result in
a high quality release without the need for a "p1"!

On Tue, Oct 5, 2010 at 2:39 AM, Mark Burgess <mark.burg...@iu.hio.no> wrote:

>
> Release candidate cfengine-3.1.0 beta 1 is now available from
>
> http://www.cfengine.org/pages/source_code
>
> MD5 862bc71846106d5dfb2367d73c21d5de
> SHA1 38199b1562ec0ba533700e8c34c5faf0e53664a2
>
> This is expected to be the final release, subject to only minor
> modifications.
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------
> This version will contain major changes to the handling of client public
> keys, and a number of bug fixes.
> Keys are now stored using a unique hash, removing the need for storage
> by hostname or IP address.
> Keys should be converted automatically on execution.
>
> Some Key Changes include
>
>        New package policy addupdate - installs package if not there and
>        updates it otherwise.
>
>        New special function readstringarrayidx, similar to readstringarray,
>        but uses integer indices. Very useful if first row elements are
>        not good identifiers (e.g. contains spaces, non-unique, etc.).
>
>        Change two log formats to use time() instead of date()
>        - filechanges
>        - total compliance
>
>        Change in storage of public keys. Cfengine now hashes the public
> key and uses this
>        as the keyname.
>
>        The old dynamic addresses lists are deprecated.
>        Caching of dns and key information for greater server speed.
>        Change in last-seen format reflects the public key usage.
>
>        Change from using md5 to sha256 as default digest where possible.
>
>        Commands not returning 0 in commands-promises are flagged
>        as repair_failed.
>

Could this also be an option where acceptable return codes are specified as
a list, and anything not in that list is repair_failed?


>
>        Redesign of the knowledge map infrastructure.
>
>        Allow disable to set 000 permissions
>
>        Allow special value "cf_null" in lists, which is a blank to be
> skipped over. Allowed initialization of NULL lists.
>
>        Regular expression anchoring respected properly during pattern
> replacement
>
>        These server features are now deprecated:
>
> http://www.cfengine.org/manuals/cf3-reference.html#hostnamekeys-in-server
>
>
> http://www.cfengine.org/manuals/cf3-reference.html#dynamicaddresses-in-server
>
>
> --
> Mark Burgess
>
> -------------------------------------------------
> Professor of Network and System Administration
> Oslo University College, Norway
>
> Personal Web: http://www.iu.hio.no/~mark
> Office Telf : +47 22453272
> -------------------------------------------------
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@cfengine.org
> https://cfengine.org/mailman/listinfo/help-cfengine
>
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to