From owner-freebsd-stable@freebsd.org Sat Nov 2 18:14:19 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 53EE71AE919 for ; Sat, 2 Nov 2019 18:14:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4756dk1frwz41xM for ; Sat, 2 Nov 2019 18:14:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x732.google.com with SMTP id 71so13799465qkl.0 for ; Sat, 02 Nov 2019 11:14:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zMu6row261TRT81n4jEY+nQooopOfiVBzXOGWzJDHLI=; b=Hgs/+OikjefZyq4oheBw62BhIX8BXHM7vIDw88T/xzJQjN/V5qo/zO2Z/SMLrx1f3T FS/G8GT/MSwhLTAbnmCjjeLgtZy0OTGoyovQBem0aNF8fuRBsIy2A4lel5YZonC5aiZK WQ3gjHwJA+ubr5dpMHbw2DTVK7m3ksJbnVmXL7G3oOe1WGEcxE6pvXHh0lshHEvP3E1q VH/ydshBBiXgp/qStdJ/gHpfv/N7b/DhpNStCCXaMocB02sGfsDm9anTz+DDu1t76Buf wIA44zWQbZ5UyKjmfR8mCSBJY/d9K3XCNzD8Mq2SZudyNA2taTirEWOHzbQjYzogtiwS 0hwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zMu6row261TRT81n4jEY+nQooopOfiVBzXOGWzJDHLI=; b=dobwLoswFma9rAJKP64iRJ54UNdsCm9yw+dLkHH0KdELiLuyhqVFSIW3IOwB9210ex iZBYe7MEleNte5HYPhR8hrvqxN6CCv5k/Cztu6Cv1gR1RS98BotJ/J8m6ZiReyLyDrak qKz5wzbIywKPuLvA0Azus2bsKkyPfmWBTl4HtNBNd+tx2KBZPqqZ/AUeP5bF7z/geUIE Tb9lP3Xr6dEM6mMailmo0kEJXOyRrNkApF0OmtOdxpNHA5JflNyxUSQsIhkvIEksEvYu vGXV8c1K9s5C69V3ENz6HRjM4KmfNfK3K+EdMqScpNavNbd+TYF5x+zXaz4Uetu7FaSw 1ejA== X-Gm-Message-State: APjAAAW5HKodJXKb0aLSEcyyBAVctPuOgHXET6ABZZRH/V+scmEOXTTk 6/kOhwIc55RjhmvGSVJa5gka8A4Q5QI+JXDviyubxm86wx8= X-Google-Smtp-Source: APXvYqxEQ6gySiQnNzTkR0jxNW/D/WANncxFktYRxy6+s6vaeYvjWh0OgyCsQDOkQUh1w2q4h1L40Gz8Pusrw+HlHng= X-Received: by 2002:a37:4e41:: with SMTP id c62mr8286844qkb.215.1572718456723; Sat, 02 Nov 2019 11:14:16 -0700 (PDT) MIME-Version: 1.0 References: <20191025000552.GF51072@FreeBSD.org> <20191101134418.GW12076@FreeBSD.org> <20191101145250.GR1424@FreeBSD.org> <20191102141250.GA17205@FreeBSD.org> <20191102161829.GE5599@FreeBSD.org> In-Reply-To: <20191102161829.GE5599@FreeBSD.org> From: Warner Losh Date: Sat, 2 Nov 2019 12:14:05 -0600 Message-ID: Subject: Re: 12.1-RELEASE schedule update To: Glen Barber Cc: "Sergey A. Osokin" , FreeBSD Release Engineering Team , FreeBSD-STABLE Mailing List X-Rspamd-Queue-Id: 4756dk1frwz41xM X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=Hgs/+Oik; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::732) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.78 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.78)[ip: (-9.44), ipnet: 2607:f8b0::/32(-2.38), asn: 15169(-2.03), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2019 18:14:19 -0000 On Sat, Nov 2, 2019 at 10:20 AM Glen Barber wrote: > On Sat, Nov 02, 2019 at 02:12:50PM +0000, Sergey A. Osokin wrote: > > On Fri, Nov 01, 2019 at 02:52:50PM +0000, Glen Barber wrote: > > > On Fri, Nov 01, 2019 at 01:44:18PM +0000, Sergey A. Osokin wrote: > > > > At the moment we have graphics/drm-fbsd12.0-kmod port for 12.0. > > > > I hope in most cases it's enough for RELENG_12 branch, however > > > > just to avoid a potential confusion I see the following options > > > > we can do: > > > > > > > > - create a new port for 12.1 only > > > > - rename the existing port to drm-fbsd12-kmod > > > > - rename the existing port to drm-fbsd12.1-kmod (in case of 12.0 EoL) > > > > > > What about using the meta-port and keying off of OSVERSION? > (Personally > > > I have no real preference either way, nor with any of the solutions you > > > propose above.) > > > > Actually we have one, graphics/drm-kmod, and it depends on the following > one: > > > > .elif ${OSVERSION} >= 1200058 && ${OSVERSION} < 1300000 > > RUN_DEPENDS= ${KMODDIR}/drm.ko:graphics/drm-fbsd12.0-kmod > > ... > > > > So, in case we don't expect an API/ABI changes in 12.x branch we can > > just rename it to drm-fbsd12-kmod, or create a specific version of > > the port for 12.1 - drm-fbsd12.1-kmod and update the meta-port as well. > > > > We should never expect this type of ABI/KBI breakage along a stable > branch. (That is our definition of "stable", technically, but sometimes > there are unexpected breakages that occasionally go undetected.) > The KPIs that drm depends on are quite specific and weird and aren't part of the set we guarantee (and we can't do what drm needs to do with only the 'safe' ones). It's not much different than virtual box which also has this issue frequently because it too falls into that category. > > > Also, since this is repeatable thing for every upcoming release > > > > we can add this point to the check list and release scheduling. > > > > > > Yes, good idea. Just let us know how you want to proceed, and we can > > > add a note to the documentation. > > > > I mean I believe we should that (create a new port, update the meta-port, > > etc.) in advance, in the beginning of the first phase of release cycle. > > > > This seems like a reasonable approach. > How do we get packages from the new port into the release so that users don't install the 12.0 port by mistake? Warner