From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP Testing report week 40 and 41
Date: Fri, 13 Oct 2017 16:46:23 +0200 [thread overview]
Message-ID: <59E0D1BF.30706@codethink.co.uk> (raw)
Hi,
this report will be short since we have been concentrated on the release.
++ CIP kernel maintenance
* Intensive patch review to release a new kernel in the coming days,
before ELCE.
** Renesas related patches tests in order to include support in the
kernel, so later on in B at D. The plan is have it ready for the training
session.
++ CIP Testing project
* Moved from Jessie to Stretch as Guest OS. #152
** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/152
* B at D v1.0 Release
** Please check the high level task to follow the process #141
*** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/141
** Gold Master declared. Working on the deployment.
*** Release date/time announced: Wed 1th Oct. 2017 12:00 UTC
* B at D 101 training session preparation in progress
** Follow the progress in #126
*** Link: https://gitlab.com/cip-project/cip-testing/testing/issues/126
* Daily tests report from LAVA keep being sent daily to
cip-testing-reports mailing list.
++ Other activities
* Tom Pollard is helping us on the training session preparations.
Welcome Tom.
* CIP developers meeting at ELCE announced.
* Next week toscalix will be at the AGL AMM.
* ELCE talk (Ben H. and toscalix) preparation in progress.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2017-10-13 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 14:46 Agustin Benito Bethencourt [this message]
2017-10-13 15:10 ` [cip-dev] CIP Testing report week 40 and 41 Agustin Benito Bethencourt
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=59E0D1BF.30706@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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