[chef-dev] Re: releases, github milestones, etc.

[Thom May < >]

Hey Phil,

that one didn't make it to 12.3.0 because we'd already cut the RC last week. I've not had a chance to look at it fully yet, but if it's urgent we'll either pick it up in 12.3.1 or 12.4 in a couple of weeks.

In general, we're using the issue milestones "Accepted Minor" for work that we think aren't breaking changes, "Accepted Major", for things that we think will be breaking changes or major work, and "Help Wanted", for issues that we'd like help from the community with. We've been publishing the list of Help Wanted issues to the chef-dev list as we assign things to that bucket.

Hope this helps,

-Thom

On Mon, Apr 27, 2015 at 9:15 PM, Phil Dibowitz < " target="_blank"> > wrote:

Heya devs,

This has come up tangentially in a few PRs, but I think it deserves a real
discussion.

How are we handling github milestones and releases - because it seems a lot
like milestones are not actually paid attention to in releases.

As an example, I tagged https://github.com/chef/chef/pull/3235 with 12.3.0
because it's a bugfix to 12.2.x and 12.3.0 came out today sans that.

So if we don't pull in all things with a milestone of X into an X release -
how do we actually as a team know what's going into a release? Shouldn't
everything with a milestone either be merged or someone post and say "I don't
think this is necessary for release X because of reason Y, can we schedule for
release X+1?" and then we change the milestone it's tagged with?

--
Phil Dibowitz                              ">
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Be who you are and say what you feel, because those who mind don't matter
 and those who matter don't mind."
 - Dr. Seuss