Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F1190F5DC for ; Mon, 15 Apr 2013 21:00:46 +0000 (UTC) Received: (qmail 77771 invoked by uid 500); 15 Apr 2013 21:00:46 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 77706 invoked by uid 500); 15 Apr 2013 21:00:46 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 77697 invoked by uid 99); 15 Apr 2013 21:00:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Apr 2013 21:00:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dch@jsonified.com designates 209.85.217.179 as permitted sender) Received: from [209.85.217.179] (HELO mail-lb0-f179.google.com) (209.85.217.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Apr 2013 21:00:40 +0000 Received: by mail-lb0-f179.google.com with SMTP id t1so4978881lbd.38 for ; Mon, 15 Apr 2013 14:00:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jsonified.com; s=google; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=vtjCKYj11BC3wIyPexAnYMF6z0fdMFr+mXVsbRsWuGM=; b=UY7dmeDP+qjF8giU+VqMDdjT0FsB04rtXhMQCF6ezjXzK0JCIS2z/u1D+9hRzol4/I Rxeg+TjOhxa5xAhAWj8i+sb0dhn9n9WFa5vOZCG5h5mVa35FkcwVtLlpgUFOqE4OONqi WW5Wk7LeujyEflclx49LvcevzHtI3Xqd+VHdI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=vtjCKYj11BC3wIyPexAnYMF6z0fdMFr+mXVsbRsWuGM=; b=DdRvGZXY4Tlbfy+oO7DKViXhwvEME0P3ABiXlFG4lHgfKqB4oZ9Cz9hDW72yLtS+8d AUoHlPe2MCGGyhOUJV34lAO3/nYQ3OU/CgQa4Zxb8efKq6kJ0EXwWNPnDvlDJoeQE937 ut/PeCQwnm8sEzApuXkZ1ZUNnx+SNjD7vTnZ0M3k+z0z3Q9leogLfsJr42qQ6GsPTvpI am+FvoOSwfj4Vlnja4uH0uWN3jpQrrylKGVYbEQjJj9zGeJmB4llP4XBcqFWdMg8evCa g8EXeS4U6qnw3R5hxVpglRgqll+fAzW55r3bXHjBIhecRgARZhDIVUT/R8ECU/6ymf53 4PAQ== MIME-Version: 1.0 X-Received: by 10.112.199.194 with SMTP id jm2mr17330lbc.21.1366059618759; Mon, 15 Apr 2013 14:00:18 -0700 (PDT) Received: by 10.112.149.73 with HTTP; Mon, 15 Apr 2013 14:00:18 -0700 (PDT) X-Originating-IP: [84.112.19.176] In-Reply-To: References: <848572a115b1470ab2ae13fed4364f8d@git.apache.org> <5097e5984caa405abee1da702b0eb7b0@git.apache.org> Date: Mon, 15 Apr 2013 23:00:18 +0200 Message-ID: Subject: Re: [4/6] git commit: updated refs/heads/1.3.x to 5e64395 From: Dave Cottlehuber To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlF/sLzLgHCVn8UuZ4ZRD1fc66wFggueJ1B31jfAW2tqt2Ucz5KTn0/J9QDVLaDvG4Xa5TB X-Virus-Checked: Checked by ClamAV on apache.org On 15 April 2013 20:30, Jan Lehnardt wrote: > > On Apr 10, 2013, at 02:52 , wendallc@apache.org wrote: > >> Refactor javascript runner script to handle couchdb restarts. Single interpreter per test. >> >> >> Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo >> Commit: http://git-wip-us.apache.org/repos/asf/couchdb/commit/9838eef7 >> Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/9838eef7 >> Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/9838eef7 >> >> Branch: refs/heads/1.3.x > > Can you update NEWS & CHANGES with the test suite updates in all the relevant branches? > > Thanks! :) > Jan > -- > PS: We should really address not having to do this manually anymore. Noah, would now be > a good time rethinking all this? Now is a good time. Alex has some nice refactoring work that *hint* could be pushed to an asf branch Real Soon Now, and we can roll this into it. In principle what we would need are 2 things: - discplined workflow (oh noes) to ensure that all CHANGES-worthy work has a corresponding update in .rst files, with a suitable `version-added` tag. - some nifty python to pull those version-added tags into a section in the generated docs I can write up the first part, but I'm not comfortable with the 2nd bit, assuming its the right approach. Any takers? A+ Dave