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

[Phil Dibowitz < >]

On Thu, Apr 30, 2015 at 05:49:55PM +0100, Thom May wrote:
> I don't think that's realistic though; that hypothetical contributor can't
> make a good judgement on whether their contribution is gonna go into a
> patch release or has to be held until the next major version.
> That said, I think it is reasonable to have a tag that allows the
> contributor to nominate regressions.

Many contributors won't... but if you're not even looking at milestones, how
are you even sure you're merging in the things *you* want to merge to a given
release. We need a consistent way to tag stuff for a release so that Chef can
do a search, ensure everything is merged.

Let's say there was a regression in the RC and I sent a PR, merge it, and tag
it for release, but you don't merge it. Oops, now we just released a
regression we didn't have to. The argument of "oh, but we'll know about the
regression so we'll cherry pick it ourselves" isn't acceptable. The whole
point of having maintainers and open development system is so there's
transparency and consistency. EIther we're using milestones in GH or we're
not, but we need a system that's consistent.

-- 
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

Attachment: signature.asc
Description: Digital signature