Clara, I updated the QA Test Plan according to what we decided today. Waiting for the decision to keep one single IDAS GE (with different agents) or split it in one GE per agent (this is up to ATOS to decide), I have: 1) *restored the original line* to be consistent with the tests we have done (restored GE version available at that time, listed in the notes the actual agents versions tested) Please ALL to check the status values I set according to my knowledge and interpretation of the evolution. 2) *added the new line* for the updated versions of agents. I report here again my request to keep as GE version (in the Catalogue) *only* the usual 3-digit pattern X.Y.Z ... following the previous row I reported here 6.x.x ... but you can update it with the proper sprint number of release of those agents/version. Please find in the note field the list of updated versions and the two agents/version tested by Non Functional. Please ALL to check the status values I set according to my knowledge and interpretation of the evolution. The file is now consistent again ... given that ALL partners check the status of their tests. Let me know in case of doubt. KR Davide 2018-02-02 17:25 GMT+01:00 Davide Dalle Carbonare < davide.dallecarbonare at eng.it>: > Yes, please, share with your colleagues my message ... so that they can > comment. > > For me it's fine to have them as separated GEs, but are they different > implementations of the same APIs (so different GEi of the same GE)? or do > they have different APIs (so different GEs)? > > Up to you to decide which is the best way, but at the end I guess we have > to converge and have one single number as version and not something like > the list we have now. > > my 2 cents :-) > talk to you soon, ciao > Davide > > > > 2018-02-02 16:13 GMT+01:00 Pezuela, Clara <clara.pezuela at atos.net>: > >> I don’t have probably the right opinion about that, but if you want an >> overall version for IoT Agents you should contact TEF and my colleague from >> Atos (Jose Gato) to agree on a common numbering together. >> >> >> >> I see this specially difficult to find an overall version when each IoT >> Agent is potentially done by different owners as it will be case for IoT >> Agents from now on. >> >> >> >> IDAS is not anymore a component as a whole but a set of modules (lib and >> IoT Agents) that should be labelled individually, in my opinion. >> >> >> >> The only what I wanted to remark here is that IoT Agents have to be >> labelled at functional level, since now the version is in the Catalogue. >> >> >> >> Maybe the solution would be have each of them as a single GE. >> >> >> >> Best regards >> >> >> >> Clara Pezuela >> >> Head of IT Market >> >> Research and Innovation Group >> >> ARI booklet >> <https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf> >> >> Atos Spain SA >> >> Clara.pezuela at atos.net >> >> +34 675 62 9974 <+34%20675%2062%2099%2074> >> >> >> >> [image: cid:7206F4B45C675D4FA60A576B4DAED2AE at mail.sis.atos.net] >> >> >> >> *From:* Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] >> *Sent:* Friday, February 02, 2018 4:05 PM >> *To:* Pezuela, Clara >> *Cc:* fiware-qualityassurance at lists.fiware.org >> *Subject:* Re: Label IDAS >> >> >> >> Hi Clara, >> >> I've seen the changes you have done in the QA Test Plan ... and let me >> say that those changes are a bit confusing ... let me explain. >> >> >> >> You have changed the columns "GE version in the FIWARE Catalogue", "GE >> version actually tested" (originally: "UNAVAILABLE", "5.x.x") with >> something different (punctual versions of IDAS components). >> >> The original line was already tested by us with 3 out of 4 components at >> a different version. *This line is no more consistent.* >> >> I prefer to keep the original one and create a new line with the new >> versions (even if some are the same as before). Components versions can be >> listed in the Notes column. >> >> >> >> In addition ... >> >> When a GEi has different components that evolve independently (with their >> own versions) I would be more in favor to give to the GE (the group) one >> sigle version number. This would help us (and all FIWARE Community) to >> avoid confusion. >> >> >> >> Given said that we are now starting to test the updated components. >> >> >> >> I would fix the inconsistency that we have in the QA Test Plan ... how do >> see my comments? >> >> >> >> Thank you, >> >> Davide >> >> >> >> >> >> >> 2018-02-01 15:09 GMT+01:00 Pezuela, Clara <clara.pezuela at atos.net>: >> >> Hi Davide, >> >> >> >> FIWARE Catalogue has been updated with version of IDAS: >> https://catalogue.fiware.org/enablers/backend-device-management-idas >> >> >> >> I have updated the QA spreadsheet, so now we can label the IoT Agents. I >> have already the non functional labels, could you please give the >> functional ones to calculate global one? >> >> >> >> You can see in labels excel that we need to label the IoT Agents by >> separated as they are 3 different components. Please bear in mind >> >> >> >> Best regards >> >> >> >> Clara Pezuela >> >> Head of IT Market >> >> Research and Innovation Group >> >> ARI booklet >> <https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf> >> >> Atos Spain SA >> >> Clara.pezuela at atos.net >> >> +34 675 62 9974 <+34%20675%2062%2099%2074> >> >> >> >> >> >> >> >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. >> As its integrity cannot be secured on the Internet, the Atos group >> liability cannot be triggered for the message content. Although the sender >> endeavors to maintain a computer virus-free network, the sender does not >> warrant that this transmission is virus-free and will not be liable for any >> damages resulting from any virus transmitted. >> >> Este mensaje y los ficheros adjuntos pueden contener información >> confidencial destinada solamente a la(s) persona(s) mencionadas >> anteriormente y pueden estar protegidos por secreto profesional. >> Si usted recibe este correo electrónico por error, gracias por informar >> inmediatamente al remitente y destruir el mensaje. >> Al no estar asegurada la integridad de este mensaje sobre la red, Atos no >> se hace responsable por su contenido. Su contenido no constituye ningún >> compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. >> Aunque se esfuerza al máximo por mantener su red libre de virus, el >> emisor no puede garantizar nada al respecto y no será responsable de >> cualesquiera daños que puedan resultar de una transmisión de virus. >> >> >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. >> As its integrity cannot be secured on the Internet, the Atos group >> liability cannot be triggered for the message content. Although the sender >> endeavors to maintain a computer virus-free network, the sender does not >> warrant that this transmission is virus-free and will not be liable for any >> damages resulting from any virus transmitted. >> >> Este mensaje y los ficheros adjuntos pueden contener información >> confidencial destinada solamente a la(s) persona(s) mencionadas >> anteriormente y pueden estar protegidos por secreto profesional. >> Si usted recibe este correo electrónico por error, gracias por informar >> inmediatamente al remitente y destruir el mensaje. >> Al no estar asegurada la integridad de este mensaje sobre la red, Atos no >> se hace responsable por su contenido. Su contenido no constituye ningún >> compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. >> Aunque se esfuerza al máximo por mantener su red libre de virus, el >> emisor no puede garantizar nada al respecto y no será responsable de >> cualesquiera daños que puedan resultar de una transmisión de virus. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20180206/31fda482/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4796 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20180206/31fda482/attachment-0002.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4796 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20180206/31fda482/attachment-0003.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy