From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] no 3.3.8-4 yet
Date: Mon, 18 Jun 2012 12:52:35 -0400 [thread overview]
Message-ID: <CAA93jw4-9L6524oGxz06wYVm4ch8DcUVPLTPW+bUFDDS__PDXg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7icDw52-Ketzx0g6sKkEtLi4mvGgy4x6YJ9JZJeFb4Dg@mail.gmail.com>
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äht
> SKYPE: davetaht
> http://ronsravings.blogspot.com/
--
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/
next prev parent reply other threads:[~2012-06-18 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 2:24 Dave Taht
2012-06-18 16:52 ` Dave Taht [this message]
2012-06-19 10:58 ` Maciej Soltysiak
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=CAA93jw4-9L6524oGxz06wYVm4ch8DcUVPLTPW+bUFDDS__PDXg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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