On 10/24/25 15:37, David Rowley wrote:
> On Sat, 25 Oct 2025 at 04:51, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>>
>> On 10/24/25 08:00, Ron Johnson wrote:
>>> On Fri, Oct 24, 2025 at 10:54 AM Adrian Klaver
>>> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>>
>>> "Never trust a .0 release with important data" is just as true in 2025
>>> as it was in 1985.
>>>
>>> That's a chicken and egg problem, though, isn't it?
>>
>> There is nothing stopping you from setting up a test instance and
>> kicking the tires on a new release to see if your setup will work
>> correctly.
>
> I'd say it's exactly that attitude that causes people to think .0
> should be avoided. Beta versions are meant for test instances. It'd be
> good if people encouraged their use more often rather than pushing
> people to defer til GA.
1) From previous posts to this list folks have mentioned their
organizations prohibit touching anything less then a GA or maybe a late
RC. That comes from on high and I doubt the folks issuing the orders are
on this list.
2) The attitude comes from lessons learned in the School of Hard Knocks.
Until someone or someones can guarantee a new GA release will not eat
your data or spring security leaks then the prudent thing to do is wait
to see what happens when it hits the world at large. I learned this
lesson, pitfalls of jumping into something new, across fields outside of
software as well. In other words 'new and improved' is not always the
case, see 737 MAX as case in point.
3) Progress happens and you need to keep up. A little caution is good
thing though, especially if you are the one who is being held
responsible for any adverse outcomes.
>
> David
--
Adrian Klaver
adrian.klaver@aklaver.com
