From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id BFC9D2001A1 for ; Mon, 13 Feb 2012 15:08:47 -0800 (PST) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id q1DN8faR005435; Mon, 13 Feb 2012 15:08:41 -0800 Date: Mon, 13 Feb 2012 15:08:41 -0800 (PST) From: david@lang.hm X-X-Sender: dlang@asgard.lang.hm To: Dave Taht In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] Coming up with a naming scheme for releases 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, 13 Feb 2012 23:08:48 -0000 On Mon, 13 Feb 2012, Dave Taht wrote: > I've put up a draft of how I think future releases will work. Please > comment. > > http://www.bufferbloat.net/projects/cerowrt/wiki/Release_Strategy > > I still want to prototype it to get a better workflow - automated > continuous builds > in particular, also finding a way to build for x86, VMs, and maybe one other > (preferably arm) architecture (guruplug? suggestions wanted) > > I frankly admit to having some fondness for having codenames like > 'ocean city' and 'paris' > rather than the proposed scheme, but what I have there represents > reality better, > at least at this point. doing a topic branch as --x or similar will work as well, with minimal confusion. David Lang