[Fiware-iot] Actions to manage quickly

[thierry.nagellen at orange.com]

Hi Tobias,

To answer your questions:

1.       No change regarding the planning of release. R3.2 is closed since end of December 2013 with software delivery but we have to manage now the peer-review of the associated documentation (official deliverables planned for 31-01-2014). We are now in sprint R3.3.1 but no delivery is expected at the end of January.

2.       Green, Yellow and Red colors are just for me to manage the different releases and to point out that we will have less time to modify or validate anything because the end of the project is closer for the different minor releases. (bug correction or integration between GEs will be more difficult for features in R3.3)
BR
Thierry

De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu]
Envoyé : vendredi 17 janvier 2014 15:08
À : NAGELLEN Thierry IMT/OLPS; fiware-iot at lists.fi-ware.eu
Cc : Salvatore Longo; Raihan Ul-Islam
Objet : RE: Actions to manage quickly

Hi Thierry,

I have two questions

1)      (FI-WARE general) has there been a change in the release schedule? Because when I look at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates I am reading that release 3.2 has been at the end of December.
We actually released version 3.2 of the NEC IoT Broker there, and we are not planning another release at the end of January, because the R3.3 require more substantial work.

2)      (IoT Broker specific) Is there an explanation why in the spreadsheet the lines regarding the R3.2 features are marked yellow? The Unit test plan covers these features.
Best regards
Tobias

From: fiware-iot-bounces at lists.fi-ware.eu<mailto:fiware-iot-bounces at lists.fi-ware.eu> [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>
Sent: Dienstag, 14. Januar 2014 22:06
To: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: [Fiware-iot] Actions to manage quickly
Importance: High

Hi All,

I will be in Brussels tomorrow for FI-Ware, pushing GEs to EC EIP team, the team who manages the SCC calls for Smart Cities. We would have the opportunities to explain in infodays that Cities can use FI-Ware GEs for future projects and services.

So I'm not able to manage the IoT weekly meeting but we have some urgent issues. The most critical is the status of R3.2 delivery planned for End of January. We have to provide all elements for internal review: software packages available, and the 3 guides also available

·         Unit Testing Plan with new tests for the new features implemented in R3.1 and R3.2

·         Installation and Administration Guide: reading this document a newcomer is able to install everything to have a running instance of your GEi

·         User and Programmer Guide: both should understand how to use your GEi after reading your document

You can find in the attached file the status for IoT: we are far to reach the right level of quality. For some GEi this is the first round so it is normal that some improvements have to be done (typically for SAP) but some documents are missing (Fraunhofer, Atos). So please check in detail everything, I've tried to provide some quick comments focusing on what are the main points to improve.
Send me an email if you have any question and we can have P2P telco on Thursday to go through the docs.

It was difficult to identify some features and I need validation that everything for Protocol Adapter ZPA will be done for R3.3 so maybe never achieved because after GEis discussion during the last review... And typically the backlog is not always aligned with the features and the expected release described in the IoT Technical Roadmap. So next point will be again the improvement of the backlog.
About what we have to stop and what could continue, we are waiting for a general email from Juanjo to all GEi owners after some clarifications from our PO.

In the same time, we have to revise the Technical Roadmap for R3.3. We agree for a common sentence for the features we will not be able to develop because the Commission asked us to stop the development but in a first step, check that the existing features are correctly dispatched between the different R3.X releases and if needed update R3.3 and the backlog accordingly.

BR
Thierry
Thierry Nagellen
Program Manager Future Internet
Orange Labs Networks & Carriers
905 rue Albert Einstein
06921 Sophia Antipolis Cedex
+33 492 94 52 84
+33 679 85 08 44


_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20140117/0050b46f/attachment.html>