From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Update 2017week10: kernel maintenance / kernel testing
Date: Tue, 7 Mar 2017 18:07:50 +0100 [thread overview]
Message-ID: <58BEE8E6.3060100@codethink.co.uk> (raw)
Dear CIP friends,
as you know we released the beta version of Board at desk - Single dev
on Feb 22nd a little before the CIP at ELC. It was announced through
this mailing list.
That day we also communicated the first draft of the kernel maintenance
policies Ben H. published on our wiki[1]. The policies are an extension
from the current Linux kernel ones, having our use case in mind.
Check Yoshi's slides[2] from ELC
Christos Karamitsos has been of a great help in order to solve some
technical issues during the past few weeks, working full time to help
Don Brown to solve them. Thanks Christos. Robert Marshall is back in the
team to focus the coming weeks in preparing the 1.0 release,
substituting Christos. Welcome back again Robert.
Ben H. will be helping us in shaping the VM for his needs as kernel
maintainer the coming days. He is coming to our HQ in Manchester, UK for
this purpose.
Based on the feedback received after the beta release, we have added
some features requests in our ticket system[3]. I will be processing
them this week.
After FOSDEM, OS Leadership Summit and ELC, including the beta release,
we will go back this Friday to our bi-weekly report about the technical
activities related with kernel maintenance and testing.
[1]
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
[2]
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipconferences
[3] https://gitlab.com/cip-project/testing/issues
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
reply other threads:[~2017-03-07 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=58BEE8E6.3060100@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