From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [CIP Testing WG] Status update - 26/11/18
Date: Wed, 28 Nov 2018 14:07:04 +0000 [thread overview]
Message-ID: <6599348.piSthsvPYI@linux-if6s> (raw)
In-Reply-To: <874lc2c03e.fsf@ctlt579.codethink.co.uk>
Hi,
On Tuesday, 27 November 2018 09:59:33 GMT Robert Marshall wrote:
> Thanks Chris for the update!
>
> Chris Paterson <Chris.Paterson2@renesas.com> writes:
>
> >
> > # B at D #
> >
> > - Robert has continued to close down issues on GitLab [1] that are either fixed or won?t be fixed in time for his retirement.
> >
> > - Now that access to the AWS storage has been restored, the plan is to upload a new version of the B at D ?box? [2] that includes all the changes that
> > have been done since v1.0 was released.
>
> As mentioned on the #cip channel the new version is now in place and has
> been tested. Agust?n - can I go ahead and update the wiki?
Sure, go ahead please. Thanks for asking.
> Will we also
> need all the subsidiary packages up there too? Or is it maybe better to discuss
> face to face tomorrow as to what and how the page should look?
Do not wait. Take a decision and go for it. You have what we did the previous release as example.
Best Regards
--
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy. See https://www.codethink.co.uk/privacy.html
prev parent reply other threads:[~2018-11-28 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 11:13 [cip-dev] [CIP Testing WG] Status update - 26/11/18 Chris Paterson
2018-11-27 9:59 ` Robert Marshall
2018-11-28 14:07 ` Agustín Benito Bethencourt [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6599348.piSthsvPYI@linux-if6s \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.