Opscode Ticket Triage 11/16


#1

Hey Chefs!

Phew. I feel like I’ve been living in github and JIRA for two days
straight. We’ve been doing a ton of housekeeping on pull requests and
providing new users with information about the process. I’m pretty
happy with our progress. Unfortunately github and JIRA don’t provide
enough metrics for pretty graphs.

As you’re probably already aware, Dan recently pushed 0.10.6.RC.1.
We’ll probably ship that on Monday, barring any blocking regressions.
What will it take to get you to try it this weekend? I’m willing to
barter.

Have you noticed the new home page on the community site? It’s a great
place to send people getting started and appropriately acts as an
index to community resources. That project is finally getting some
love and we’ve got a stream of projects in the work, so don’t take a
nap or anything.

http://community.opscode.com/

Remember Omnibus? We’re right in the midst of some heavy testing on
the client, so there will be a wider beta in a few days.

Merge:
CHEF-2716 - package provider - on upgrade, no check for candidate is nil
CHEF-2705 - knife[:ssh_attribute] is ignored
CHEF-1547 - Apt provider can’t install packages from different default release
CHEF-2598 - create_on_missing does not work with remote directory resource
COOK-822 - apache2::default should allow user to specify module
recipes to include via an attribute.
COOK-815 - Nagios Config Changes Kill Nagios If Config Goes Bad

Other:
CHEF-2708 - Cloud.com Cloudstack support in knife
Closed - Upstream released this project
CHEF-2706 - The user resource does not include the -rm parameter on
the usermod command when "supports :manage_home=>true"
Commented - Author needs CLA
CHEF-1912 - As a chef user I want to load all my data bags and items
from files with one command
Commented - Author needs CLA
CHEF-2715 - Provide alternate chef-client location when bootstraping
Commented - Further discussion surround how to refactor start_chef
and bootstrap_context


Bryan McLellan | opscode | senior systems administrator
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org


#2

On 21:48 Thu 17 Nov 2011, Bryan McLellan wrote:

Phew. I feel like I’ve been living in github and JIRA for two days
straight. We’ve been doing a ton of housekeeping on pull requests and
providing new users with information about the process.

Thanks for doing this work. I wasn’t aware about the chef process until
after my pull request had been sitting for a month+, oops :frowning:

If I write a github bot that justs closes all pull requests immediatly
with a link to the how to contribute would that be helpful? Or better
yet use the Jira API to create a CHEF issue everytime a pull request is
opened without a CHEF-BLAHBLAH string in it.

Brandon

#3

On Wednesday, November 30, 2011, Brandon Philips wrote:

On 21:48 Thu 17 Nov 2011, Bryan McLellan wrote:

Phew. I feel like I’ve been living in github and JIRA for two days
straight. We’ve been doing a ton of housekeeping on pull requests and
providing new users with information about the process.

Thanks for doing this work. I wasn’t aware about the chef process until
after my pull request had been sitting for a month+, oops :frowning:

If I write a github bot that justs closes all pull requests immediatly
with a link to the how to contribute would that be helpful? Or better
yet use the Jira API to create a CHEF issue everytime a pull request is
opened without a CHEF-BLAHBLAH string in it.

Great ideas. We were talking about this today at the Community Summit.

I don’t think we would want to close them immediately but we should develop
something to auto-respond to a pull-request with a standard blurb and a
link to the How to Contribute page on the wiki. I wouldn’t want to create a
JIRA ticket because if the user has already properly created a ticket than
we would have duplicates. I would like to encourage:

  • Creating a ticket on JIRA is always the first step

  • Pull requests should contain a link to the JIRA ticket

  • Conversation regarding the issue and the fix should be on the ticket, and
    longer conversations may be on the mailing list, but we should limit the
    conversation on the pull requests. This way others can easily find the
    whole conversation without having to be familiar with all the tools.

If you could write something I would be appreciative and happy to run it.

Bryan

On Nov 30, 2011 9:44 AM, “Brandon Philips” brandon.philips@rackspace.com
wrote:

On 21:48 Thu 17 Nov 2011, Bryan McLellan wrote:

Phew. I feel like I’ve been living in github and JIRA for two days
straight. We’ve been doing a ton of housekeeping on pull requests and
providing new users with information about the process.

Thanks for doing this work. I wasn’t aware about the chef process until
after my pull request had been sitting for a month+, oops :frowning:

If I write a github bot that justs closes all pull requests immediatly
with a link to the how to contribute would that be helpful? Or better
yet use the Jira API to create a CHEF issue everytime a pull request is
opened without a CHEF-BLAHBLAH string in it.

   Brandon