[OmniOS-discuss] stable vs "bloody"
Eric Sproul
esproul at omniti.com
Tue Oct 9 10:22:08 EDT 2012
On Mon, Oct 8, 2012 at 7:00 PM, Paul B. Henson <henson at acm.org> wrote:
> Terminology wise, "stable" sounds better than "bloody" ;), but if you turn
> that around and call them "stale" and "fresh" it gives a different
> connotation :). It looks like stable includes upstream illumos-gate from
> about 5 months ago, whereas bloody is at the moment fully up-to-date with
> the current upstream. Generally, illumos-gate is intended to be production
> quality at all times, so arguably you're more stable tracking it more
> closely. There's only been a couple of times in the past year or so a commit
> broke anything of note, and I think both of those times it was caught pretty
> quick and backed out or resolved.
Hi Paul,
We run "stable" in production at OmniTI. We're also currently working
on the next stable release, intended to come out in a couple of weeks,
which will look eerily similar to what bloody is today...
That said, "bloody" is more than just "fresher illumos-gate". It's
also newer versions of the other bits we add to make the complete OS,
including gcc, OpenSSL, zlib, libxml2, and many others. Those may not
work correctly together or have bad bugs, but the goal is to let folks
try out the bleeding edge and ferret those out in the ~6 months
between stable releases.
I'm starting to collect a list (as a wiki page) of the things we want
to push into bloody after this month's release, so if I forget to post
that to the list (and IRC) please remind me. :) I know that gcc 4.7
is on that list.
Eric
More information about the OmniOS-discuss
mailing list