From: Yuri Bushmelev <jay4mail@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2010-11-12
Date: Mon, 15 Nov 2010 23:22:10 +0300 [thread overview]
Message-ID: <201011152322.10481.jay4mail@gmail.com> (raw)
In-Reply-To: <AANLkTimg9YUNRoh+Qs8-jahK8mAJzpcEk9WiUOBFVNAz@mail.gmail.com>
Hello!
> >> After my first week of doing some testing branch test builds I was
> >> thinking, would some form of either automated result submitting or
> >> form-based result submitting be a good idea? We could try and use a
> >> google doc spreadsheet / form, for example. Thoughts?
> >
> > I'll prefer to use our oestats-server to auto-publish builds data.
> > Oestats have complete information about builds.
>
> If someone has the time to update the oestats-server to provide
> summary data in a tabular form, that would be great.
I would to spend some time to look into oestats-server/client code, but it
will happens after release anyway.
> Alternatively, using forms on a google spreadsheet is an interesting
> idea. I had not thought of forms as a way that we could get anonymous
> build data with requiring a google account. Then again, I'm not sure
> how we would keep the form from being spammed, other than perhaps
> hiding it.
My opinion is to leave things as is up to release (about 2-3 weeks).
IMHO, we should concentrate now on intensive build testing and testing on
target machines.
--
Yury Bushmelev
next prev parent reply other threads:[~2010-11-15 20:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 5:17 testing branch 2010-11-12 Cliff Brake
2010-11-14 18:11 ` Frans Meulenbroeks
2010-11-14 18:38 ` Tom Rini
2010-11-14 19:23 ` Yury Bushmelev
2010-11-14 20:32 ` Tom Rini
2010-11-15 15:46 ` Gary Thomas
2010-11-15 15:47 ` Cliff Brake
2010-11-15 18:07 ` Tom Rini
2010-11-15 20:22 ` Yuri Bushmelev [this message]
2010-11-18 22:13 ` Cliff Brake
2010-11-19 9:11 ` Petr Štetiar
2010-11-19 9:43 ` Frans Meulenbroeks
2010-11-19 10:16 ` Yury Bushmelev
2010-11-19 10:36 ` Petr Štetiar
2010-11-29 19:04 ` Cliff Brake
2011-01-04 10:36 ` Steffen Sledz
2011-01-07 14:17 ` Cliff Brake
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201011152322.10481.jay4mail@gmail.com \
--to=jay4mail@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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