Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 3.0.0 #116

Merged
merged 2 commits into from
Dec 13, 2013
Merged

Release 3.0.0 #116

merged 2 commits into from
Dec 13, 2013

Conversation

blkperl
Copy link
Contributor

@blkperl blkperl commented Dec 12, 2013

No description provided.

This caused problems with the mcollective module release, reverting
until this is proven to be a safe change.
@puppetlabs-jenkins
Copy link
Collaborator

Can one of the admins verify this patch?

1 similar comment
@puppetlabs-jenkins
Copy link
Collaborator

Can one of the admins verify this patch?

@hunner
Copy link
Contributor

hunner commented Dec 13, 2013

👍

Backwards-incompat change was restrict parameter array no longer taking the keyword restrict

Final release of 3.0, enjoy!

The major change in this release is that `restrict` no longer requires you to
pass in parameters as:
`restrict` no longer requires you to pass in parameters as:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd probably change "no longer requires" to "no longer allows" unless it does allow the old way (which wouldn't be backwards incompatible) just to clarify.

apenney pushed a commit that referenced this pull request Dec 13, 2013
@apenney apenney merged commit 76d8346 into puppetlabs:master Dec 13, 2013
@blkperl blkperl deleted the release-300 branch December 13, 2013 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants