From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.1 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AC6FAC2D0A8 for ; Mon, 28 Sep 2020 13:57:52 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3B78D21548 for ; Mon, 28 Sep 2020 13:57:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="ae/sKckr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3B78D21548 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:59968 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kMtf5-0007Ut-BP for qemu-devel@archiver.kernel.org; Mon, 28 Sep 2020 09:57:51 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kMtXz-0007pX-4Q for qemu-devel@nongnu.org; Mon, 28 Sep 2020 09:50:32 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:43600) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1kMtXv-0006gG-4p for qemu-devel@nongnu.org; Mon, 28 Sep 2020 09:50:30 -0400 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1601301023; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type; bh=ipvPW611OrDCvB3SbdRMt8cKP/3naZupo4AIySzu3r8=; b=ae/sKckrrbDThRj0ZpkfDyEzkZ4f7Aq4W/PuZgzveAAuzCtjvHPXbRV3mxaKbeS3sMoC6O a5xcT41fRo2fm0FaZd23B71d8ldXTcZeLqcJTCBa1HuSUavqzgYf5G6DScMcHFMyfnkIKD HwRXiF04/LCIQCjRKqzrjoNvf8l5xIs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-536-l659EukePbetM9mDxjpY8g-1; Mon, 28 Sep 2020 09:50:08 -0400 X-MC-Unique: l659EukePbetM9mDxjpY8g-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0DCCE80733A; Mon, 28 Sep 2020 13:50:07 +0000 (UTC) Received: from redhat.com (ovpn-114-24.ams2.redhat.com [10.36.114.24]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 500107366E; Mon, 28 Sep 2020 13:50:02 +0000 (UTC) Date: Mon, 28 Sep 2020 14:49:58 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: qemu-devel@nongnu.org, Michael Roth Subject: Publishing docs for formal releases Message-ID: <20200928134958.GG2230076@redhat.com> MIME-Version: 1.0 User-Agent: Mutt/1.14.6 (2020-07-11) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=berrange@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Received-SPF: pass client-ip=63.128.21.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/28 03:47:08 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.687, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Cc: Peter Maydell , Stefan Hajnoczi Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" We currently have a cronjob publishing: https://www.qemu.org/docs/master/ The URL was chosen such that we would also publish docs for each release at URLs like https://www.qemu.org/docs/5.0.0 The latter part has not happened yet. IIUC, we first introduced the new docs approach in 4.0.0, so ideally we would publish our historical docs for 4.0.0 releases onwards, including each minor point release on stable branches. So this means 4.0.0, 4.0.1 4.1.0, 4.1.1, 4.2.0, 4.2.1, 5.0.0, 5.0.1 and 5.1.0. What needs to happen to turn this into reality ? On IRC it was sugggested that this be done as part of the release process handled by Michael Roth. Is there anything blocking this ? One we have docs publishing happening, then we'll want to also update https://www.qemu.org/documentation/ to link people to the docs for each release when making a release. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|