From owner-freebsd-questions@freebsd.org Fri Jun 16 01:52:17 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 C9352BF3C22 for ; Fri, 16 Jun 2017 01:52:17 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 8E02A67E22 for ; Fri, 16 Jun 2017 01:52:17 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: by mail-io0-x233.google.com with SMTP id k93so22024354ioi.2 for ; Thu, 15 Jun 2017 18:52:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=1dV9PdmKVgiGCxLJxZCnMCZMxM/9GIvM+qnaK/Iod7o=; b=ZSZYbyJI4+E+QDjQIHBEH+ZsHePxfSZO9/5Oz1sMY0zBRanAMBKSkJ2vNKmCi4zpLP rrZ10ZeW1McXtVW8U6VXd/TdHCkCAKOUHasUr7nWtxDYQtb6gVBauTWsiosXLwIizATF PujDwOLBxN5j0Oe70vE5m5uMuTxi0wZnE1QRKenFxm9NFmwZdLKRcnwpjIyUw4pbTjgP a8cT2RN5a7lk+dzB/o/x6uFlx5Ez7OkLOlbdykGj6rucsfN4JMTFe/QDBQLmppuoPDPo Fufa+Y5yU/KU5/NyFvDhullf2Z+0+OsP+YcC5JouBiUWBqBYpLxWDV0RkCaAUHlEaPU0 Y9wQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=1dV9PdmKVgiGCxLJxZCnMCZMxM/9GIvM+qnaK/Iod7o=; b=KJmULoHqhB4rMXOl59dWN90X4YQHgNyZf1ouVvtRmElp3gJl0xOx7GWm5f+qIta3oe yAze1k1KztKs8z/6naPY/+95p9gpCcV9UZ3vQboEFFq+tK97X13Xcyxntlf/EKqQHEL/ VzZ/2lAkWS7bx7giXcMmKlh519D8mVjaVYHDWMgx6js/mlJ/daMVPTaigW3jzHEURChK wfsMUubjaxhZWFL2mdoywJQQgwPtfUEyd/pPkqYLQROCQRsdKgryHKiYgsEiMX8EiTyv pVLJE5478I9/0EWdzjpa4khM2WKt5WM+32eXfvbjwyTq2y14lNm4ejnhZURFB5MI3BBA Dheg== X-Gm-Message-State: AKS2vOwiBw5tZktTQ1SNRmWu+yEeVeYC79sBUNwx/cH6zsj69tCkBCj0 GFeaopNiB7hZfrTG X-Received: by 10.107.34.206 with SMTP id i197mr8307983ioi.67.1497577936762; Thu, 15 Jun 2017 18:52:16 -0700 (PDT) Received: from localhost.localdomain (50-243-4-3-static.hfc.comcastbusiness.net. [50.243.4.3]) by smtp.googlemail.com with ESMTPSA id z64sm485244ioe.61.2017.06.15.18.52.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jun 2017 18:52:16 -0700 (PDT) Subject: Re: 11.1 ISO-IMAGES for alpha, beta and RC builds To: freebsd-questions@freebsd.org References: <5942EB59.8040807@gmail.com> <6be7fab4-4e34-8adf-4f03-c8c59a3e544e@FreeBSD.org> <5943356C.8060205@gmail.com> From: JD Message-ID: <594339CF.1090907@gmail.com> Date: Thu, 15 Jun 2017 19:52:15 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: <5943356C.8060205@gmail.com> Content-Type: text/plain; charset=windows-1252; 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:52:17 -0000 On 06/15/2017 07:33 PM, Ernie Luzar wrote: > 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. In my previous experiences of downloading ISO images of STABLE, CURRENT, the output of uname -a always contained the version name - i.e. STABLE or CURRENT. I do not recall downloading pre-release ISO's.