From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] no 3.3.8-4 yet
Date: Tue, 19 Jun 2012 12:58:58 +0200 [thread overview]
Message-ID: <CAMZR1YAcWPAHXBp6fUmv=amC61Zqqn86N_dyPLt5Av8sHnwuAg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4-9L6524oGxz06wYVm4ch8DcUVPLTPW+bUFDDS__PDXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]
Hi Dave,
About crystalizing dev builds. I think we could have a small set of
conditions for clear "dev" builds, say:
"at least 4 out of 5 dedicated testers reporting they could run it for at
least 48 hours without crashes, unplanned reboots or unexpected network
behaviour".
You could setup a recurring meeting in our calendars to put in place
something like this:
a) you build on every 4th thursday
b) testers fetch/install next friday
c) testers run it for the weekend
d) testers report on Monday
e) dave decides wheter to make it a solid dev build or not.
I can be a tester, I've been using various builds for some time now, they
really work for me.
One positive comment on functionality:
I no longer have to IPTABLES -I FORWARD -j ACCEPT to allow my wired TV to
discover my wireless media server client and DLNA works OK. (I know, it's a
lazy/insecure way of fixing it)
All the best!
Maciej
On Mon, Jun 18, 2012 at 6:52 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 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/
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 3310 bytes --]
prev parent reply other threads:[~2012-06-19 10:59 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
2012-06-19 10:58 ` Maciej Soltysiak [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='CAMZR1YAcWPAHXBp6fUmv=amC61Zqqn86N_dyPLt5Av8sHnwuAg@mail.gmail.com' \
--to=maciej@soltysiak.com \
--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