summaryrefslogtreecommitdiff
path: root/CHANGELOG
AgeCommit message (Collapse)Author
2013-05-10Update Modulefile, CHANGELOG for version 4.1.0Ryan Coleman
This commit alters the module metadata to indicate a 4.1.0 version release for the Puppet Forge. It contains backwards compatible features, refactors and bug fixes. CHANGELOG updated by JJM
2013-04-12Update gemspec, Modulefile, CHANGELOG for 4.0.2Jeff McCune
Without this patch the information displayed on rubygems.org does not clearly convey the intent of the Gem format of stdlib from the official puppet module format of stdlib. This is a problem because end users might get confused and start installing stdlib from rubygems.org This patch addresses the problem by making it clear that the gem version of stdlib is not intended for end users, but rather is specifically intended to make it easier for other module authors to depend on stdlib and have that dependency automatically resolved using a Gemfile. [ci skip]
2013-04-11Update gemspec, CHANGELOG, Modulefile for 4.0.1Jeff McCune
2013-04-11Update Modulefile, README, CHANGELOG for stdlib-4.0.0Jeff McCune
2012-11-28Update Modulefile, CHANGELOG for 3.2.0Jeff McCune
2012-11-28Merge branch '2.x' into 3.xJeff McCune
* 2.x: Update Modulefile, CHANGELOG for 2.6.0 Conflicts: CHANGELOG Modulefile
2012-11-28Update Modulefile, CHANGELOG for 2.6.0Jeff McCune
2012-10-25Merge branch '3.1.x' into 3.xJeff McCune
* 3.1.x: Update CHANGELOG, Modulefile for 3.1.1
2012-10-25Update CHANGELOG, Modulefile for 3.1.1Jeff McCune
2012-10-25Merge branch '2.x' into 3.xJeff McCune
* 2.x: Update Modulefile, CHANGELOG for 2.5.1 Conflicts: CHANGELOG Modulefile
2012-10-25Update Modulefile, CHANGELOG for 2.5.1Jeff McCune
2012-10-25Revert "Revert "Merge branch '2.5.x' into 3.0.x""Jeff McCune
This reverts commit 9e8c60a8b73fd96393b08d690c7197e62aae623e. This was an error on my part. 3.1.x descends from 3.0.x _and_ 2.5.x, but 3.0.x does not descend from 2.5.x. I should not have merged 2.5.x into 3.0.x, instead I should have merged 2.5.x into 3.1.x skipping over the 3.0.x merge up. I'm slowly starting to understand the implications of semver on our branching strategy... =)
2012-10-25Merge branch '3.0.x' into 3.1.xJeff McCune
* 3.0.x: Revert "Merge branch '2.5.x' into 3.0.x"
2012-10-25Revert "Merge branch '2.5.x' into 3.0.x"Jeff McCune
This reverts commit c8c7afc7a00aaeeddea6514d9fe9508513e53a73, reversing changes made to 03ec16e291a70ac5ac412be36ae3b86a771b98af. This was a mistake on my part. 2.5 is a minor release and minor releases should never be merged into patch level branches. 2.5.x should have been merged into 3.1.x instead.
2012-10-25Merge branch '3.0.x' into 3.1.xJeff McCune
* 3.0.x: Conflicts: CHANGELOG Modulefile
2012-10-25Merge branch '2.5.x' into 3.0.xJeff McCune
* 2.5.x: Update Modulefile, CHANGELOG for 2.5.0 Explicitly load functions used by ensure_resource re-formatting Add better docs about duplicate resource failures Handle undef for parameter argument Add function ensure_resource and defined_with_params Revert "Revert "Merge branch 'haus-add_pe_facts_to_stdlib' into 2.4.x"" Revert "Merge branch 'haus-add_pe_facts_to_stdlib' into 2.4.x" Prevent undefined method `split' for nil:NilClass with pe_foo_version facts (maint) Clear all facts before each example Add spec tests for pe_version facts Add PE facts to stdlib Conflicts: CHANGELOG Modulefile spec/spec_helper.rb
2012-10-25Update Modulefile, CHANGELOG for 3.1.0Jeff McCune
2012-10-25Merge branch '2.5.x'Jeff McCune
* 2.5.x: Update Modulefile, CHANGELOG for 2.5.0 Conflicts: CHANGELOG Modulefile
2012-10-25Update Modulefile, CHANGELOG for 2.5.0Jeff McCune
2012-08-16Update CHANGELOG, Modulefile for 3.0.1Jeff McCune
2012-08-16Update CHANGELOG, Modulefile for 3.0.0Jeff McCune
2012-08-14Update Modulefile, CHANGELOG for 2.4.0Jeff McCune
2012-05-23Update CHANGELOG, Modulefile for 2.3.3Jeff McCune
2012-05-10Update CHANGELOG for 2.3.2 releaseJeff McCune
2012-03-29Merge branch '2.2.x' into 2.3.xJeff McCune
* 2.2.x: (#13494) Specify the behavior of zero padded strings Update CHANGELOG, Modulefile for 2.1.3 Conflicts: CHANGELOG Modulefile
2012-03-29Merge branch '2.1.x' into 2.2.xJeff McCune
* 2.1.x: Update CHANGELOG, Modulefile for 2.1.3 Conflicts: CHANGELOG Modulefile
2012-03-29Update CHANGELOG, Modulefile for 2.1.3Jeff McCune
2012-03-13Update CHANGELOG and Modulefile for 2.3.1Jeff McCune
2012-03-12Update CHANGELOG, Modulefile for 2.3.0 releaseJeff McCune
2011-12-30Update CHANGELOG and Modulefile for 2.2.1Jeff McCune
2011-12-30Merge branch '2.1.x' into 2.2.xJeff McCune
* 2.1.x: Update Modulefile CHANGELOG for v2.1.2 release Conflicts: CHANGELOG Modulefile
2011-12-30Update Modulefile CHANGELOG for v2.1.2 releaseJeff McCune
2011-11-08 * v2.x:James Turnbull
Update CHANGELOG and Modulefile for v2.2.0
2011-08-18Update CHANGELOG, README and Modulefile for v2.1.1Jeff McCune
2011-08-18Update CHANGELOG, README and Modulefile for v2.1.1Jeff McCune
2011-08-17Update CHANGELOG, Modulefile and README for 2.1.0Jeff McCune
2011-08-08Update CHANGELOG and Modulefile for 2.0.0 releaseJeff McCune
2011-08-04Update CHANGELOG and Modulefile for 1.1.0Jeff McCune
2011-08-04Update CHANGELOG and README for 1.0.0Jeff McCune
2011-06-21Update CHANGELOG and version for 0.1.7Jeff McCune
2011-06-15Update CHANGELOG for version 0.1.6Jeff McCune
2011-06-03Update CHANGELOG for 0.1.5Jeff McCune
2011-05-26Update CHANGELOG with stage re-orderingJeff McCune
2011-05-25Update CHANGELOG for 0.1.3 releaseJeff McCune
2011-05-24Update changelog for version 0.1.2Jeff McCune
Also add release process information.
2011-05-24Add changelog to track releasesJeff McCune
Following the development process, as new releases of this module are cut the Changelog will be updated.