From nobody Sun Feb 25 00:24:25 2024 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Tj4J81tmHz5Btyg for ; Sun, 25 Feb 2024 00:24:40 +0000 (UTC) (envelope-from freebsd@shaneware.biz) Received: from mail-relay3.dca2.superb.net (mail-relay3.dca2.superb.net [66.148.95.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tj4J805jZz4qSN for ; Sun, 25 Feb 2024 00:24:40 +0000 (UTC) (envelope-from freebsd@shaneware.biz) Authentication-Results: mx1.freebsd.org; none Received: from ppp230-11.static.internode.on.net ([203.122.230.11] helo=[192.168.9.155]) by mail-relay3.dca2.superb.net with esmtpsa (TLS1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (envelope-from ) id 1re2Jh-00038o-QJ; Sat, 24 Feb 2024 19:24:31 -0500 Message-ID: Date: Sun, 25 Feb 2024 10:54:25 +1030 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Best way to have a FreeBSD VM for automated testing? To: Jo Durchholz , virtualization@freebsd.org References: <163e57a9-0b61-414c-a8f7-109f5ac90f69@durchholz.org> <7e5bc32c-dddb-4d33-96e9-99a955eed572@durchholz.org> <9b115e8e-dd8d-491a-9493-ee1ad1a8cc75@durchholz.org> Content-Language: en-AU From: Shane Ambler In-Reply-To: <9b115e8e-dd8d-491a-9493-ee1ad1a8cc75@durchholz.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Score: -1.6 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14361, ipnet:66.148.95.0/24, country:US] X-Rspamd-Queue-Id: 4Tj4J805jZz4qSN On 25/2/24 07:05, Jo Durchholz wrote: > On 24.02.24 20:19, Paul Vixie wrote: >> <> bandwagon anyway.>> >> >> Not new. Been in production for years now. > > I admit I was going by assumptions, based on the fact I had never heard > about it before, despite having been in the CI/CD treadmill for a few > years. > >> https://github.com/firecracker-microvm/firecracker > > Hm. > V 1.0.0 came out in Jan/Feb 2022, so in that sense, it's somewhat new. > > Might have been in production use in pre-1.0.0 versions, of course. > I tend to assume software exists starting with 1.0.0, pre-1.0 versions > tend to be very experimental and/or require handholding by the engineers > that are building it. > Of course, for a shop like AWS, that's not always the most accurate > assumption :-) Took me a while, but I have let go of waiting for 1.0 releases. If it works - use it, if it breaks - help make it better, otherwise you just re-invent the wheel to get what you want. How long was openssl in wide use before 1.0 ? There is always something to fix and something to add. Tagging a release or build as v1.0 is only a decision, it isn't a certainty of stability. I have about 20% of installed pkgs with a version starting with 0 -- FreeBSD - the place to B...Software Developing Shane Ambler