From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 3130F200840 for ; Mon, 18 Jun 2012 09:52:37 -0700 (PDT) Received: by wejx9 with SMTP id x9so7621613wej.16 for ; Mon, 18 Jun 2012 09:52:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=CkwJyUa6QFahAZMYdWYELBsBZ32Km7DUVwyt+6YFT6g=; b=IPcSrDLQnWIqOBGGJ6Mj1zz7NSwfAj4RB7t2ZFffmt5y8FUZA9XiMRRubgatJX682O dYxFybRizmWBQZU1H788fYyqWb2Dz2qwiRcba+36mDJuvDiMPdT+L86YCA+RTPvShbYY egIvZ38ERvFptexOD52ucrrgAq2TYEVIjJvTwO+TQqLDQYYtZ2mbhLsP0hKi11v+3tCb kU1qxLfcx3xnN+RaPnwUcXxVHrmR5RMf7P+XBLTXXgt9wuV+C2tjnzBFsB6I6wDoX0ET CLVzcuTmnmp/05dnm79RvbURuQCiZs4nEQlU2cppl7MpO5ZcOvnZr79I2t650hAoTyai 6hxQ== MIME-Version: 1.0 Received: by 10.180.84.35 with SMTP id v3mr2342085wiy.20.1340038355248; Mon, 18 Jun 2012 09:52:35 -0700 (PDT) Received: by 10.223.103.199 with HTTP; Mon, 18 Jun 2012 09:52:35 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Jun 2012 12:52:35 -0400 Message-ID: From: Dave Taht To: cerowrt-devel@lists.bufferbloat.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cerowrt-devel] no 3.3.8-4 yet X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 16:52:37 -0000 One thing that might work better from my perspective is breaking things into a string of "dev" releases and then trying to do CI on them more automatedly without any testing by me. ...except when I break the package db with the new opkg support, and the fw rules aren't forwarding right right now I really hate to waste other people's time with stuff that is entirely untested however. My overall policy has been to integrate the release, adding new features, bug fixes, etc, then testing for at least 24 hours on several routers including my main one, then do an announcement that it was "safe" to try it, with what the new features are. Lately people have been beating me to the announcements... That said, cutting that cycle down would speed matters up and reduce my workload. I feel that if I establish a clear "dev" vs "somewhat safe for real use" set of builds things would go faster for everyone, and those that really want to be on the utterly bleeding edge can be. Does that work? > -- > Dave T=E4ht > SKYPE: davetaht > http://ronsravings.blogspot.com/ --=20 Dave T=E4ht SKYPE: davetaht http://ronsravings.blogspot.com/