Hi, I may have some of this wrong, so take this with a grain of salt, please.
On 04/20/2015 09:34 PM, Vince Skahan wrote: > puppetlabs-release-pc1-0.9.2-1.el7.noarch I think this package only sets up the puppetlabs repos for you. Its versioning has literally nothing to do with *contents* of those repos. Syncing it to current puppet stable would likely contradict semver. > puppet-agent-1.0.0-1.el7.x86_64 I believe this is the version of the AIO agent package. This kind of packaging is new, and apparently it was decided to start its versioning at 1. This might be sensibly synced with the core version, yes. > puppetserver-2.0.0-1.el7.noarch Puppet Server is a new-ish product that just launched last year. Syncing its version to that of core puppet would most definitely contradict semver, unless we keep bumping the versions on both. > > # puppet --version > 4.0.0 Truth. > > > # cfacter --version > 0.4.1 (commit e9333e184e57106f7ce3fb6b44b05656f417d245) > # facter --version > 2.4.3 > # hiera --version > 2.0.1 While tightly interwoven with Puppet, facter and hiera have always developed independently and are versioned independently. In the future, it might be desirable to lift all of these to one version that could then be applied to the All-In-One package as well, but such measures have implications. > # mco --version > /opt/puppetlabs/bin/mco 2.8.1 MCO is related to Puppet, but not part of it per se. > # puppetserver --version > puppetserver version: 2.0.0 See above. Hope this clears things up a little. As for your issues with the documentation, would you raise these as bugs in Jira? Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/55390851.1020002%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
