- From: Phil Dibowitz <
>
- To:
- Subject: [chef-dev] releases, github milestones, etc.
- Date: Mon, 27 Apr 2015 13:15:53 -0700
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
Attachment:
signature.asc
Description: Digital signature
- [chef-dev] releases, github milestones, etc., Phil Dibowitz, 04/27/2015
Archive powered by MHonArc 2.6.16.