[Fiware-security] [Fiware] Delivery of GEs

Miguel Carrillo mcp at tid.es
Wed Nov 27 13:24:49 CET 2013


Hi,

The initial message by Juanjo equally mentioned R3, not specifying if this meant R3.2 or the whole R3. I am just echoing an old one. But it seems that it was not clear enough so you raising this was useful. Hope all is clear now.

If you see the timing, depending on the review date after April, the reviewers may have R3.2 or the whole R3, and this is something we will have to leave with. We may like M33 or not, but the commitments of the DoW are between each partner and the EC, not just the coordination, and the DoW is clear in this respect.

Best,

Miguel


El 27/11/2013 13:07, TRABELSI, Slim escribió:
Sorry Miguel,

But in your e-mail (see below) you were mentioning R3 .. for me (and I'm not the only one) R3 means the whole R3 and not 3.2.

Thank you for your clarification.
Best
Slim



From: fiware-security-bounces at lists.fi-ware.eu<mailto:fiware-security-bounces at lists.fi-ware.eu> [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo
Sent: mercredi 27 novembre 2013 12:02
To: fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>
Subject: Re: [Fiware-security] [Fiware] Delivery of GEs

Dear all,

A reminder goes attached, as it seems that we are overlooking that the deadline was fixed by the project coordinator and sent to all weeks ago. I was just mentioning this once again, not fixing anything new.

Of course we expect R3.2  (as we did with R2.2 and R2.3 in the past year). How could we possibly ask for the whole R3, it would not make any sense.

Best regards,

Miguel
El 27/11/2013 11:46, BISSON Pascal escribió:
Dear All,

Probably email of Miguel was not clear but ...

The sprint planning is the reference
http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates

So end of R3 is March 2014

So for December it is end of Second Minor Release of R3 aka R3.2.2.

As for the rest I remind you that instructions have been provided to work on R3.
As WPL I was responsible to create the links on the FI-WARE Private Wiki for each of the GE (R3) and their manuals.
Let me inform you this has been done.
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR3

Counting on you now to use those links for R3 of the GEs this in accordance to Technical Roadmap for R3 established (and yet to be moved to public wiki - but here will take care).

Best Regards,
Pascal


De : Seidl, Robert (NSN - DE/Munich) [mailto:robert.seidl at nsn.com]
Envoyé : mercredi 27 novembre 2013 11:17
À : ext TRABELSI, Slim; BISSON Pascal
Cc : fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>
Objet : RE: [Fiware] Delivery of GEs

Hi Pacal,
I can only support Slim here.
It is completely inacceptable that we should deliver something before the official end of the milestone (in this case even some month earlier!).

Maybe Miguel meant R3.2 instead of entire R3?
Could you please clarify it?

Greetings
Robert

From: fiware-security-bounces at lists.fi-ware.eu<mailto:fiware-security-bounces at lists.fi-ware.eu> [mailto:fiware-security-bounces at lists.fi-ware.eu] On Behalf Of ext TRABELSI, Slim
Sent: Wednesday, November 27, 2013 10:16 AM
To: BISSON Pascal (pascal.bisson at thalesgroup.com<mailto:pascal.bisson at thalesgroup.com>); fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>
Subject: [Fiware-security] FW: [Fiware] Delivery of GEs

Hi Pascal,

We don't the content of this e-mail !

Release R3 should takes place at sprint 3.3.3 in some cases according to the plan. But the dead-line fixed by Miguel for the 15 of December for the R3 release does not correspond to the planning that we made and that we agreed on. In the DOW the last deliverable is due to M33.
So why should we deliver on December knowing that nothing is ready ?

We maybe misunderstood the message ?

Thank you
Best
Slim





From: fiware-bounces at lists.fi-ware.eu<mailto:fiware-bounces at lists.fi-ware.eu> [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of Miguel Carrillo
Sent: mardi 26 novembre 2013 17:57
To: fiware at lists.fi-ware.eu<mailto:fiware at lists.fi-ware.eu>
Subject: [Fiware] Delivery of GEs

Dear all,

A clarification that was asked yesterday in the course of the last WPL/WPA call

We fixed a deadline to deliver R3 and the associated manuals by the 15th of December.

But of course nothing precludes an early delivery. If someone wants to coordinate with their WPL and release before that, we can simply perform the review of the manuals of a given GE on the private wiki (same procedure as usual) and publish it in advance once approved, before the bulk of R3. Once all this is approved, a given GE could also be added early to the catalogue.

As we follow an agile methodology<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology>, delivering at the end of each time frame(mapped to calendar months  here<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates>)  is always an option . But a delivery has to be consistent, this means that:

  *   We need a consistent delivery: manuals & sw must be synchronised (if we have the R3 software and the wiki has the R2 manuals, this is a problem!)
  *   We need to have the internal reviews as usual: we cannot take things to the public wiki without prior approval
  *   Same about the catalogue: once the software and manuals are ready, the entry on the catalogue will have to be updated and will undergo reviews as well.
Please centralise this with your WPL who, as usual,  should provide his feedback and internal review. Once internally cleared, he will let us know that there is a given GE in their chapter delivering early.

Best regards,

Miguel




--

----------------------------------------------------------------------

     _/          _/_/                     Miguel Carrillo Pacheco

    _/   _/     _/  _/   Telefónica       Distrito Telefónica

   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 9

  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N

 _/          _/_/                         28050 Madrid (Spain)

                                          Tel:  (+34) 91 483 26 77



                                          e-mail: mcp at tid.es<mailto:mcp at tid.es>



Follow FI-WARE on the net



        Website:  http://www.fi-ware.eu

        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

        Twitter:  http://twitter.com/Fiware

        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932

----------------------------------------------------------------------

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx



_______________________________________________

Fiware-security mailing list

Fiware-security at lists.fi-ware.eu<mailto:Fiware-security at lists.fi-ware.eu>

https://lists.fi-ware.eu/listinfo/fiware-security



--

----------------------------------------------------------------------

     _/          _/_/                     Miguel Carrillo Pacheco

    _/   _/     _/  _/   Telefónica       Distrito Telefónica

   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 9

  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N

 _/          _/_/                         28050 Madrid (Spain)

                                          Tel:  (+34) 91 483 26 77



                                          e-mail: mcp at tid.es<mailto:mcp at tid.es>



Follow FI-WARE on the net



        Website:  http://www.fi-ware.eu

        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

        Twitter:  http://twitter.com/Fiware

        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932

----------------------------------------------------------------------

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx


--
----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito Telefónica
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 9
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N
 _/          _/_/                         28050 Madrid (Spain)
                                          Tel:  (+34) 91 483 26 77

                                          e-mail: mcp at tid.es<mailto:mcp at tid.es>

Follow FI-WARE on the net

        Website:  http://www.fi-ware.eu
        Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
        Twitter:  http://twitter.com/Fiware
        LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20131127/fd107660/attachment.html>


More information about the Old-Fiware-security mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy