From owner-freebsd-questions@freebsd.org Fri Jun 16 01:33:21 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC76BBF360F for ; Fri, 16 Jun 2017 01:33:21 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6936674D2; Fri, 16 Jun 2017 01:33:21 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id i7so21896518ioe.1; Thu, 15 Jun 2017 18:33:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=B8zZeSQmFKnZH3bIHI2nivmKB3csx/TNJJt8nymDzvw=; b=ZzCZKAzhnX2huJEKI6y827/ewKYnrpWVY/gWALvZaqy25ZFMfRNve99L2lJCdbnIhc rQUsrxVpE8EVhWEtOizhjySWWod8sTHF2OBiKWC2hwqQFRcBm7xgwOy2Q1YYsp6NE3t3 1w3/p7Hfr4jp8KXkmuvF/P2JSjE+O5uGOCyzvdHdDzn1KNsfglKKZ3TbO6k+iSmtTr1w 3z1ZPhAPl4/rKOPg6ZDsaGfurfYGHJpRrHAk9VAkm9an+UM/Z3IGuEY567PYuQfP9bg3 GNlgmQon/dXPF3XVbbPCCJ3cKNbWV0jW8aZDWkbUdh3z6ZjT/OG+T2S+VS7dHkDo/xLt IRpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=B8zZeSQmFKnZH3bIHI2nivmKB3csx/TNJJt8nymDzvw=; b=uQ0klRGcdqlewU7xq3vRAUTftezJ9PUmYSOR+8R1ohuhltmvVw8aFyTzYXETuIxYv9 4OyNXuWu90fyDCt/8LY3f8SQNSSSaG8R5FCDzZWuL3+OwV/3pOequpLSSxz6efpGbks4 YI029fy74RUeDEabs9LpP/nDvqbL4idaSuMI2dUW1eUuFjdOs0LOtQDzUVfxhotETAlR hTwzaKx55c+rtEiFJTjsBOMmh3FYzuM+9VNiL+OFPYx6REFnxrp3n+ycL4+zhiuMOZko p4Whq9WGm+ycKY5kbkTq6n2xh6TDxkjhJzNRbcTpJyu+E9TBRoWU07rjl2Wtk4AoIDVI 4OLA== X-Gm-Message-State: AKS2vOwq27LFruDURWahMFoKvAZ8ZAPa1mFq/TXbF1Rb8lN183sE08EO yKhlrFUMoC9iDjEL X-Received: by 10.107.138.224 with SMTP id c93mr8802143ioj.32.1497576800994; Thu, 15 Jun 2017 18:33:20 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-89-70.neo.res.rr.com. [74.141.89.70]) by smtp.googlemail.com with ESMTPSA id c31sm452490ioj.53.2017.06.15.18.33.20 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 15 Jun 2017 18:33:20 -0700 (PDT) Message-ID: <5943356C.8060205@gmail.com> Date: Thu, 15 Jun 2017 21:33:32 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Matthew Seaman CC: freebsd-questions@freebsd.org Subject: Re: 11.1 ISO-IMAGES for alpha, beta and RC builds References: <5942EB59.8040807@gmail.com> <6be7fab4-4e34-8adf-4f03-c8c59a3e544e@FreeBSD.org> In-Reply-To: <6be7fab4-4e34-8adf-4f03-c8c59a3e544e@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2017 01:33:22 -0000 Matthew Seaman wrote: > On 15/06/2017 21:17, Ernie Luzar wrote: >> https://www.freebsd.org/releases/11.1R/schedule.html >> >> Shows no alpha builds. Is it normal to start the release build process >> with beta builds skipping the alpha builds? >> >> I see ISO-IMAGES for 11.1 beta1. I don't remembering seeing ISO-IMAGES >> for previous alpha, beta and RC build releases. Is this a new change to >> existing procedures? Are we going to see ISO-IMAGES for alpha, beta and >> RC builds from now on? >> >> Where does snapshot prerelease fit into the alpha, beta and RC build >> process? >> >> Is this documented someplace? > > The alpha builds are internal to Release Engineering -- they're > essentially just a sanity check that the code to go into the release > doesn't have obvious problems. The beta builds are the first ones > released to the public for wider testing, once RE is satisfied that they > won't cause your machine to spit chunks of harddrive all over the floor > or other faux-pas. > > Yes, pre-release iso images have been released historically for people > to download and do test installs. It's pretty hard to get people to > test releases in any case, so making it as convenient as possible for > people to install is a good idea. > > The 'snapshot' referred to in the release schedule is a tag created in > the code repository so that the precise BETA1 or BETA2 or whatever code > can be checked out in a repeatable way. The BETAs are built against the > 11-STABLE branch in SVN, which is the main and fairly active development > branch for all 11.x code. So the BETAs could evolve quite rapidly, > although we're in a code-freeze at the moment and all commits to > 11-STABLE require RE approval. > > Once the BETAs have proven satisfactory, the 11.1-RELEASE branch will be > created. This means two things: first, and commits to 11-STABLE after > the branch point will not appear in 11.1-RELEASE unless specifically > merged (so the RE lock on commit approvals to 11-STABLE will be lifted). > Second: the release branch is effectively in feature-freeze at this > point and only fixes for issues discovered during testing will be applied. > > This is basically the same process that has been used since around > 6.0-RELEASE. > > Cheers, > > Matthew > > Thank you for the details. Let me reword this to be sure I understand what you said. All BETA, RC, and RELEASE builds have ISO-IMAGES created, and the result in the "uname -r" command will contain BETA, RC, or RELEASE as part of the OS name. Snapshots for alpha, PRERELEASE, STABLE and CURRENT builds do not have ISO-IMAGES created and the result of the "uname -r" command will contain PRERELEASE, STABLE or CURRENT as part of the OS name. Compiling of STABLE or CURRENT from source will result in the "uname -r" command containing STABLE or CURRENT in the OS name.