Commit 57cffe09 authored by Nathen Harvey's avatar Nathen Harvey
Browse files

Merge pull request #26 from opscode-cookbooks/prep_157_release

Prep 157 release
parents fc23046a b5419371
......@@ -2,6 +2,15 @@ erlang Cookbook CHANGELOG
=========================
This file is used to list changes made in each version of the erlang cookbook.
v1.5.7 (UNRELEASED)
-------------------
- Update Berksfile to use
[https://supermarket.chef.io](https://supermarket.chef.io)
- Update the `CONTRIBUTING.md` file with new URLs and information
- Update copyright date and email addresses in `README.md`
- Change 'Opscode, Inc.' to 'Chef Software, Inc.' where appropriate
- #24 - Add yum-epel recipe to install prereqs for erlang.
v1.5.6 (2014-07-29)
-------------------
#16 - Allow for systems with that do not have lsb installed
......@@ -45,7 +54,7 @@ Locking yum dependency to '< 3'
v1.3.2
------
### New Feature
- **[COOK-2915](https://tickets.chef.io/browse/COOK-2915)** - Debian codename override
- **[COOK-2915](https://tickets.opscode.com/browse/COOK-2915)** - Debian codename override
v1.3.0
------
......
......@@ -3,24 +3,21 @@
We are glad you want to contribute to Chef Software Cookbooks! The first
step is the desire to improve the project.
You can find the answers to additional frequently asked questions
[on the wiki](http://wiki.chef.io/display/chef/How+to+Contribute).
You can find additional information about
[contributing to cookbooks](http://wiki.chef.io/display/chef/How+to+Contribute+to+Chef+Cookbooks)
on the wiki as well.
[contributing to cookbooks](https://docs.chef.io/community_contributions.html)
on the Chef Docs site.
## Quick-contribute
* Create an account on our [bug tracker](http://tickets.chef.io)
* Sign our contributor agreement (CLA)
[ online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L)
(keep reading if you're contributing on behalf of your employer)
* Create a ticket for your change on the
[bug tracker](http://tickets.chef.io)
* Create an account on [GitHub](http://github.com).
* Create an account on the [Chef Supermarket](https://supermarket.chef.io/).
* [Become a contributor](https://supermarket.chef.io/become-a-contributor) by
signing our Contributor License Agreement (CLA).
* Create an [issue for your change on
GitHub](https://github.com/opscode-cookbooks/erlang/issues).
* Link to your patch as a rebased git branch or pull request from the
ticket
* Resolve the ticket as fixed
* Label your ticket as "Needs Review"
We regularly review contributions and will get back to you if we have
any suggestions or concerns.
......@@ -49,18 +46,18 @@ patches.
It only takes a few minutes to complete a CLA, and you retain the
copyright to your contribution.
You can complete our contributor agreement (CLA)
[ online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L).
You can complete our contributor license agreement (CLA)
[ online at the Chef Supermarket](https://supermarket.chef.io).
If you're contributing on behalf of your employer, have your employer
fill out our
[Corporate CLA](https://secure.echosign.com/public/hostedForm?formid=PIE6C7AX856)
instead.
[Corporate Contributor License Agreement
(CCLA)](https://supermarket.chef.io/ccla-signatures/new) instead.
## Ticket Tracker (JIRA)
## Ticket Tracker (GitHub Issues)
The [ticket tracker](http://tickets.chef.io) is the most important
documentation for the code base. It provides significant historical
information, such as:
The [ticket tracker](https://github.com/opscode-cookbooks/erlang/issues) is
the most important documentation for the code base. It provides significant
historical information, such as:
* Which release a bug fix is included in
* Discussion regarding the design and merits of features
......@@ -72,7 +69,7 @@ Each ticket should aim to fix one bug or add one feature.
You can get a quick copy of the repository for this cookbook by
running `git clone
git://github.com/chef-coobkooks/COOKBOOKNAME.git`.
git://github.com/opscode-coobkooks/COOKBOOKNAME.git`.
For collaboration purposes, it is best if you create a Github account
and fork the repository to your own account. Once you do this you will
......@@ -85,7 +82,7 @@ as the cookbook, we suggest you suffix the repository with -cookbook.
### Branches and Commits
You should submit your patch as a git branch named after the ticket,
such as COOK-1337. This is called a _topic branch_ and allows users to
such as ISSUE-22. This is called a _topic branch_ and allows users to
associate a branch of code with the ticket.
It is a best practice to have your commit message have a _summary
......@@ -93,12 +90,12 @@ line_ that includes the ticket number, followed by an empty line and
then a brief description of the commit. This also helps other
contributors understand the purpose of changes to the code.
[COOK-1757] - platform_family and style
[ISSUE-22] - platform_family and style
* use platform_family for platform checking
* update notifies syntax to "resource_type[resource_name]" instead of
resources() lookup
* COOK-692 - delete config files dropped off by packages in conf.d
* ISSUE-692 - delete config files dropped off by packages in conf.d
* dropped debian 4 support because all other platforms have the same
values, and it is older than "old stable" debian release
......@@ -110,30 +107,20 @@ to them.
### Github and Pull Requests
All of Chef's open source cookbook projects are available on
[Github](http://www.github.com/chef-cookbooks).
We don't require you to use Github, and we will even take patch diffs
attached to tickets on the tracker. However Github has a lot of
convenient features, such as being able to see a diff of changes
between a pull request and the main repository quickly without
downloading the branch.
If you do choose to use a pull request, please provide a link to the
pull request from the ticket __and__ a link to the ticket from the
pull request. Because pull requests only have two states, open and
closed, we can't easily filter pull requests that are waiting for a
reply from the author for various reasons.
Github at either
[http://www.github.com/chef-cookbooks](http://www.github.com/chef-cookbooks)or
[http://www.github.com/opscode-cookbooks](http://www.github.com/opscode-cookbooks).
### More information
Additional help with git is available on the
[Working with Git](http://wiki.chef.io/display/chef/Working+with+Git)
wiki page.
Additional help with git is available on the [Community
Contributions](https://docs.chef.io/community_contributions.html#use-git)
page on the Chef Docs site.
## Functional and Unit Tests
This cookbook is set up to run tests under
[Chef's test-kitchen](https://github.com/chef/test-kitchen). It
[Test Kitchen](https://github.com/test-kitchen). It
uses minitest-chef to run integration tests after the node has been
converged to verify that the state of the node.
......@@ -209,8 +196,8 @@ other members of the Chef community:
[chef-dev](http://lists.chef.io/sympa/info/chef-dev) mailing
lists
* #chef and #chef-hacking IRC channels on irc.freenode.net
* [Community Cookbook site](http://community.chef.io)
* [Chef wiki](http://wiki.chef.io/display/chef)
* [Supermarket site](http://supermarket.chef.io)
* [Chef Docs](http://docs.chef.io)
* Chef Software Chef [product page](http://www.chef.io/chef)
......@@ -231,10 +218,10 @@ commit message, and update the relevant ticket.
If a contribution adds new platforms or platform versions, indicate
such in the body of the commit message(s), and update the relevant
COOK ticket. When writing commit messages, it is helpful for others if
you indicate the COOK ticket. For example:
issues. When writing commit messages, it is helpful for others if
you indicate the issue. For example:
git commit -m '[COOK-1041] - Updated pool resource to correctly
git commit -m '[ISSUE-1041] - Updated pool resource to correctly
delete.'
Please do use [foodcritic](http://acrmp.github.com/foodcritic) to
......
......@@ -77,7 +77,7 @@ License and Author
* Author: Hector Castro (<hector@basho.com>)
* Author: Christopher Maier (<cm@chef.io>)
Copyright 2011-2013, Chef Software, Inc.
Copyright 2011-2015, Chef Software, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
......
......@@ -3,7 +3,7 @@ maintainer 'Chef Software, Inc.'
maintainer_email 'cookbooks@chef.io'
license 'Apache 2.0'
description 'Installs erlang, optionally install GUI tools.'
version '1.5.6'
version '1.5.7'
depends 'apt', '>= 1.7.0'
depends 'yum', '~> 3.0'
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment