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

[Lamont Granquist < >]

On 05/05/2015 09:27 AM, Phil Dibowitz wrote:
> Can we define "blessing a nightly" - there's sorta two schools of thought 
> here.
>
> The first is that nightlies are versioned as such "12.3+nightly20150501" or
> whatever, and when you want to "bless" a nightly you do a build of the same
> git hash, but with a version number (12.4).
>
> The second is that every nightly has it's own real big-boy version number like
> 12.46, 12.47 (or better yet 12.20150501, 12.20150502), and then we just update
> metadata somewhere that says one is blessed which causes it to show up in a
> different dropdown menu.
Yeah that's getting at the root problem.

The way I've understood "blessing a nightly" is that literally the 
artifact is copied over into the stable channel and there's no 
rebuilding or bumping of version numbers going on.

If we rebuild and reversion then it makes a bit more sense, then 12.3.97 
becomes 12.4.0 or something like that on release.  However, if we want 
to make a stable release off of 12.3.97 (friday's build) when we've 
already cut 12.3.98 and 12.3.99 (saturday and sunday with some stuff 
committed over the weekend we don't really want to consider 'stable') we 
need to update the version number in lib/chef/version.rb which means a 
commit off a branch starting at 12.3.97 and shipping that instead of 
shipping the release off master.  If we say you can only promo the 
latest then you've got precisely 24 hours to decide if the nightly is 
'stable' enough for stable or not, which seems like a tight timeframe...