Hi, this is the picture taken with my mobile. I assume the one taken with the camera has a higher resolution. Best regards

Hi, as output of the workshop I have created two tickets: * Add page numbers to examples output (.pdf docs): https://gitlab.com/cip-project/cip-testing/testing/issues/97 * Have a single .pdf document

Hi, kernelci interface is nice. The LAVA one is not so I guess kernelci only.

Hi Robert, can you take a couple of pictures of your laptop connected to a screen and the BBB where we can see something on the screen recognisable as B@D? I will use one for the release announcement

Hi, if you have time, specially if you are in Japan this week, please promote our open workshop through twitter, which takes place tomorrow afternoon (Japan time). Use the hashtag of the event #ossumm

Hi, I have re-arranged the topics for the workshop (proposal). If RT requires more than 15 min, we will provide it the second slot and move down the testing topic. If there is more than one topic prop

Hi Ben, versions that have not been backported Is there a technical reason for these patches not being backported or is it simply that never was requested/needed before? Based on this request, is it p

Hi, Yes we should. We should. Good question to start.

Hi, No.

Hi, The license review process has not finished so we will wait for it before releasing the testing environment. I will let you know when is done and the new release date. Best Regards

Hi, I would like to propose a discussion about the next steps ion the testing project. Please read the current plan in the CIP Testing landing page, Action 2: https://wiki.linuxfoundation.org/civilinf

Hi, Some of you might not have edit rights for the wiki. I will bring here the process to get them, meanwhile, feel free to translate the messages through the mailing mlist. I will add them to the wik

Hi, any news have a greater impact if it is communicated in the readers native language. I have published some social media messages in the wiki[1] that will be used to spread the word about the testi

Hi, Please do not spread the links on #86 before the release. The will be structured and described in the Download page and promoted on the Release Day.

Hi, So the release of B@D is scheduled for May 23rd at 11:00 UTC Now we will concentrate in the following tasks: * Deployment: #86 https://gitlab.com/cip-project/testing/issues/86 * Other release rela

Hi, Either that one or @cip-project would work. I have no strong preference.

Hi, I would like to bring back this topic now that the B@D release is coming and we will have a strong presence at OSSJ. Possible names: * @lfcip (taken) * @civilip * @civilOS (taken) * @OScip (taken)

Hi, during today's meeting, I got input from the engineers about the two ship-stoppers we have been facing the last few days: * lava-tool integration #76: https://gitlab.com/cip-project/testing/issues

Hi, We will have a meeting through hangout tomorrow Thursday at 10:00 UTC Link to the hangout: https://plus.google.com/hangouts/_/codethink.co.uk/team-event-cip?hceid=YWd1c3Rpbi5iZW5pdG9AY29kZXRoaW5rL

Hi, In phase two of the CIP testing project, we will need to sign the builds and provide them in a repo (or a place easily downloadable) so any tester can pick it up and test it, sending the report to