From: david@lang.hm
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Coming up with a naming scheme for releases
Date: Mon, 13 Feb 2012 15:08:41 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1202131506460.28034@asgard.lang.hm> (raw)
In-Reply-To: <CAA93jw42B_L7VV9bx4H0+Z+_m39Yawyi8dXt_nQqgYD_tV+YYw@mail.gmail.com>
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 <kernel>-<branch>-x or similar will work as well,
with minimal confusion.
David Lang
prev parent reply other threads:[~2012-02-13 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 22:50 Dave Taht
2012-02-13 23:08 ` david [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1202131506460.28034@asgard.lang.hm \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox