To answer your original question: yes, 6.3 is almost here.  We've been
running this schedule of twice a year releases for *decades*, so you as a
fan of stable OpenBSD releases should be familiar with the time frames by
now, no?

On Mon, Mar 26, 2018 at 8:31 PM, Z Ero <zerotetrat...@gmail.com> wrote:

> I just don't want OpenBSD to turn into Linux where the fixation is on
> newest shiny thing rather than doing code right.


*How* does that happen?  People test the builds _before_ release so that we
can iron out problems in the changes that happened over the previous six
months!  If no one tests, then it'll be a crap release and you'll be
wondering why the code wasn't done right.



> Sometimes I think
> people who are excessively interested in bleeding edge features more
> want an OS for tinkering with than an OS for production / work.


I want a box that lets me get stuff done too.  That's why when the Meltdown
issue hit the fan I tightened my belt and shoveled the shit to mitigate it
with mlar...@...and testing in snapshots was how we identified problems and
gained confidence it its stability.  Stability isn't something magical
gained just by sitting in the tree untested!  Things become stable when
people test them.  If the only people testing snapshots before release are
the developers, then the release will be stable on the developers' boxes
and not so stable on everyone else's.

I want something stable to use. But to each his own.
>

That's nice; I want my code to work on the first try.  Too bad both our
wishes require work.

If you're not testing snapshots then you're not contributing to that
stability.  Constraints in your life keep you from doing that?  Sure, fine,
but be aware that you're taking not giving, and instead of asking others
"why do you give?" you should ask yourself "how am I giving, here, in my
community, in my life, in the world?"


Philip Guenther

Reply via email to