From owner-freebsd-doc@FreeBSD.ORG Sun Mar 4 23:43:23 2012 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F2ECC1065675; Sun, 4 Mar 2012 23:43:22 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 22CFA8FC19; Sun, 4 Mar 2012 23:43:21 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so2110197wib.13 for ; Sun, 04 Mar 2012 15:43:21 -0800 (PST) Received-SPF: pass (google.com: domain of r.c.ladan@gmail.com designates 10.216.135.219 as permitted sender) client-ip=10.216.135.219; Authentication-Results: mr.google.com; spf=pass (google.com: domain of r.c.ladan@gmail.com designates 10.216.135.219 as permitted sender) smtp.mail=r.c.ladan@gmail.com; dkim=pass header.i=r.c.ladan@gmail.com Received: from mr.google.com ([10.216.135.219]) by 10.216.135.219 with SMTP id u69mr2942659wei.89.1330904601187 (num_hops = 1); Sun, 04 Mar 2012 15:43:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=OsduNfW5U9wgdB+Hukz/1PlSTIAMaS7U1PTE+Ub/wWI=; b=ttT4vksE7YE5LV6Sg+sOeE7I0kwX/dXF9RQXHl6ZJepDqdMFn1O1DZ5Mwx0/TCXFRu xhWA1nTjnyj4QknZpTXs7qbK3GaqbuMK5dLZvPKNq38mFKOy537NPaLwzFSPt2lRtkBk yF4ekwmr0LLD1jsQQkzq8U+/y5i5T7vCSi8ehsztXnCmtfJ5YOKHwt30RoHdW/+we2c5 wtJrkf6wFDiDRYHsrHVAPCjvTXvYlkvt9kT2+BcYx+qaPtsbVGD7/uOhjw56ZrEooT/O PI1hIYETcmfwpS55fncWfzmAEomdKMPOqshvFE30ytA2sH1Vgqz046ieS3kAG7HmmRwL cTJw== Received: by 10.216.135.219 with SMTP id u69mr2393033wei.89.1330902728531; Sun, 04 Mar 2012 15:12:08 -0800 (PST) Received: from [192.168.1.12] (ip18-43-209-87.adsl2.static.versatel.nl. [87.209.43.18]) by mx.google.com with ESMTPS id ep17sm16191326wid.2.2012.03.04.15.12.07 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 04 Mar 2012 15:12:08 -0800 (PST) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <4F53F6C6.1000708@freebsd.org> Date: Mon, 05 Mar 2012 00:12:06 +0100 From: Rene Ladan Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: Hiroki Sato References: <20120305.024113.1804223224441444882.hrs@allbsd.org> In-Reply-To: <20120305.024113.1804223224441444882.hrs@allbsd.org> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: doceng@FreeBSD.org, doc@FreeBSD.org Subject: Re: HEADS UP: CVS->SVN repository conversion X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2012 23:43:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04-03-2012 18:41, Hiroki Sato wrote: > Hi, > > A prototype of the CVS->SVN repository conversion of the doc and www > tree is ready for public review. It delayed by various reasons but > we need to go ahead with that direction to make it possible to merge > useful proposals which were submitted and involving large-scale > changes to the tree. > > The conversion itself will be done in a straightforward way. The > infrastructure (ACL, commit log, etc) will be almost the same as the > src tree. The difference is no SVN->CVS import will be done after > the conversion date. > [...] > > Can you please check if there is something I am missing? Please > focus on technical aspects of the conversion. Detail discussions > about how to use the converted repository such as projects/ policy, > branching, etc. should be held after we can obtain the same rendering > results from the converted repository and other automated > infrastructure for mirroring works fine as before in the FreeBSD.org > cluster. > [snip ---- http://docsvn.allbsd.org/MIGRATION.txt] So if I understand correctly the Perforce conversion, which currently depends on CVS, will also be stopped? Currently the Dutch Documentation Project uses Perforce as a staging area, i.e.: 1) Perforce Importer takes a snapshot from the current CVS tree 2) 'p4 integrate -b docproj_nl' merges upstream CVS changes into the staging area 3) edit files 4a) 'p4 submit' submits local changes to Perforce 4b) 'dcvs commit' submits local changes to CVS With SVN, things would be much easier, since projects/docproj_nl could be used as a staging area instead, with commits happening there and doing a simple 'svn merge' to the main tree when things are in shape. But from what I read the projects/ tree is forbidden area during the first few weeks. René - -- http://www.rene-ladan.nl:8080/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9T9sYACgkQjJ5keuVkK/wv4ACcDaPdKSzwWTbQzZ9l2Myniy9x 9K8AoLOfEoQevSLrkYwX9SmZygfzyjpa =YyGf -----END PGP SIGNATURE-----