Additional COOK updates


#1

Ohai Chefs,

All the COOK tickets reviewed so far this week are merged. The following
tickets are also merged. Mostly typos or really minor changes.

COOK-1128 - reference to deprecated cookbook in readme
COOK-1215 - oracle and amazon added to metadata

COOK-1643 - erlang dependency

COOK-1750 - typo in readme
COOK-1791 - add “name” to metadata
COOK-1821 - send #.to_s, I ran into this and had the same solution :slight_smile:
COOK-1843 - dont use unicode quotes
COOK-1858 - filename typo
COOK-1861 - style fix in quoting
COOK-1862 - add “name” to metadata

I’ll have another post (to chef users too) with cookbook release updates
soon - there’s over 100 tickets that are merged and not released, and
we’ll be getting releases out soon.

The new workflow that Bryan described for OSS projects will be applied to
the COOK project soon. I’ll follow-up with links to public search filters
for you to use.

Additionally, we’re working on getting why-run support added to LWRPs, and
fixing cookbooks for the new attributes changes (CHEF-1804). Those
activities are being done under our internal sprint ticketing system,
rather than the open source Jira.

Finally, if you’ve been waiting to hear if your COOK contribution will be
reviewed, we’re sorry for the delay. We’re still going through the
backlog, and we’re meeting 3 times a week. We’re inviting folks to join
the code review meetings which happen in Google+ Hangouts:

http://wiki.opscode.com/display/chef/Code+Review

You’re all awesome, and thank you for contributing to Chef and
participating in our community!


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman


#2

On 11/8/12 11:24 AM, “Joshua Timberman” joshua@opscode.com wrote:

The new workflow that Bryan described for OSS projects will be applied to
the COOK project soon. I’ll follow-up with links to public search filters
for you to use.

The COOK project is now updated to the new OSS workflow which was
described Bryan here:

http://lists.opscode.com/sympa/arc/chef/2012-11/msg00083.html

Too long, didn’t read: when you submit a new pull request, instead of
putting the ticket in “Resolved” status, just click the "Fix Provided"
button.

Search filters are created for the various states. The filter we start
with for the code review meetings:

http://tickets.opscode.com/secure/IssueNavigator.jspa?mode=hide&requestId=1
0874

This will probably be sufficient for most people: to know the tickets that
have a fix, but it hasn’t been reviewed yet.

Once a ticket’s fix is reviewed and it should be merged, it will show up
in this filter:

http://tickets.opscode.com/secure/IssueNavigator.jspa?mode=hide&requestId=1
0875

Then after the ticket has been merged into the opscode-cookbooks, it will
be here:

http://tickets.opscode.com/secure/IssueNavigator.jspa?mode=hide&requestId=1
1376

Tickets will be closed when the fix has been released in a new version of
the cookbook.