State of Puppet 3.0 and our commitment to quality

[Michael Stahnke]

As many of you have doubtless noticed, Puppet 3 and Facter 2 have been sitting
in RC (Release Candidate process) for a long time. That's about to change, but
they won't be getting released as they currently stand. Puppet 3 and Facter 2
have been pulled out of the RC process after we recognized that the performance
needed to be worked on and the reworked pluginsync was not going to solve the
problems that we had aimed for it to solve. What this means is the Facter
2.0rc and Puppet 3.0rc branches will be removed, and work will be targeted at
the Facter 2.x and Puppet 3.x branches. When they are ready for release we will
restart their rc process, continuing from the last rc tag.

In order for us to be able to concentrate on getting things right, we are going
to concentrate all of our efforts on 3.0 until it is out. After it is out we'll
move to an alternating release cadence between the Puppet 2.7/Facter 1.6 series
and the Puppet 3.x/Facter 2.x series. At this point Puppet 2.7/Facter 1.6 will
be in bug fix only mode, all new features will go into the Puppet 3.x/Facter
2.x series.

One reason for the Puppet 3 and Facter 2 (and Hiera 1) releases to to reset our
version number system to match SemVer (seehttp://semver.org for more
information about what exactly that is, if you are not familiar with it). At
the moment it is still a little bit up in the air how we are going to try to
focus work on 3.0.y bug fixes and new, backward compatible features for later
3.x versions. We'll keep you posted as we come up with a plan.

If you have questions or concerns, please let us know.

Mike Stahnke
Community Manager

[David]

Hi Mike-

Thanks for your announcement. Can you say a bit about where the hiera distribution fits into this? 

It is a little fuzzy to me during the 2.7/3.x transition which version/packages the community is supposed to use with 2.7.x in the meantime. The gem version (0.30)?, the one off HEAD in the github repos (1.0.0)?, the files in the puppetlabs repos (e.g. 1.0.0.0-01rc3 on apt.puppetlabs.com -- and hey, what about hiera-puppet 1.0.0-0.1rc1, where does that fit into the picture for the 2.7 branch?)? Thanks for any direction you can provide.

       -- dNb

[Matthaus Litteken]

David,
The hiera 1.0 rc packages or the 0.3.0 gem will work with 2.7.x. Hiera
1.0 will work with both Puppet 2.7.x and Puppet 3.x. And to answer
your other question, Hiera 1.0.0rc1 was never publicly released as a
package because a bug was found internally before it released.

Does that help answer your questions?

haus

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/lzK9pP745b8J.
>
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.



--
Matthaus Litteken
Release Manager, Puppet Labs

[David]

On Monday, July 16, 2012 3:10:28 PM UTC-4, Matthaus Litteken wrote:

The hiera 1.0 rc packages or the 0.3.0 gem will work with 2.7.x. Hiera
1.0 will work with both Puppet 2.7.x and Puppet 3.x. And to answer
your other question, Hiera 1.0.0rc1 was never publicly released as a
package because a bug was found internally before it released.

Does that help answer your questions?

Very close, and extremely helpful, thanks. I think my other question might not have been clear. It appears there are separate "hiera" and 

"hiera-puppet" packages (the latter being the one with the 1.0.0rc1 designation) in the puppetlabs devel apt repo. See http://apt.puppetlabs.com/pool/lucid/devel/h/ for what I mean. I was under the impression that hiera-puppet contained the glue code between puppet 3.x and hiera 1.x. Am I correct that 2.7.x users do not need to install it? 

If this is the case, it seems like it makes more sense to pull hiera 1.0.0 from github rather than try to get it from the devel apt repo. At least until a hiera package gets blessed into the non-devel repos. Does that sound right to you?

Thanks for your help.

      -- dNb

[Matthaus Litteken]

David,
Hiera-puppet does provide the glue between Puppet and Hiera. You need
to install both hiera and hiera-puppet if you are doing hiera lookups
in your manifests (regardless of puppet version). Hiera-puppet
provides the parser functions that are used in manifests and hiera
does the lookups.

haus

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/puppet-users/-/SFtd9eorcKUJ.

[Jeff McCune]

To follow up on this, I removed the 3.0rc branch from the main Puppet Labs repository.  Patrick and I merged the change set present in this branch into the 3.x branch itself.

This means the merge targets are now "back to normal" rather than "in release candidate."  Please review the following information for a refresher about what goes where.

If you have code that has not been merged, please follow these guidelines to answer the question, "What is my merge base?"

* Merge up will happen as: 2.6.x => 2.7.x => 3.x => master

* Bug fixes should target 2.7.x at the earliest.

* 2.6.x is only for security fixes.

* If you're developing something that should _not_ be released in 3.0.0, then use master as your merge base.  (Note, this scenario is a smell for Puppet Labs employees.  If you're working on something that shouldn't be released in Puppet 3.0.0 then please ask yourself, "Am I working on the right thing?")

* If you're working on a bug that affects 2.7, use 2.7.x as your merge base.

* If you're working on a security issue that affects 2.6, use 2.6.x as your merge base.  Only security related changes should go into 2.6.x at this point.

* For everything else, use 3.x as your merge base.

Hope this helps.

Cheers,

-Jeff McCune

[David]

Thanks for the explanation. My apologies for any thread hijacking I did (and thanks to Jeff for bringing it back on target).

        -- dNb

[Jeff McCune]

On Mon, Jul 16, 2012 at 5:11 PM, David <dnblank...@gmail.com> wrote:

Thanks for the explanation. My apologies for any thread hijacking I did (and thanks to Jeff for bringing it back on target).

You didn't hijack the thread AFAIK.  Mike asked to let us know if they had questions which is what you did.

I was just replying to the original message because I deleted the 3.0rc branch which may affect work in flight.

-Jeff