[Fiware-iot] IoT Backlog: actions to do

[MANUEL ESCRICHE VICENTE]

Hi Tarek,

Let me confirm what Laurent reported.
The workflow expects there's some verification after execution was done. If the normal worlflow wouldn't be it, please, let me know.

Additionally, Closed means it's finished.

If any other related question, please, don't hesitate to let me know.

Kind regards,
Manuel

De: "laurent.artusio at orange.com<mailto:laurent.artusio at orange.com>" <laurent.artusio at orange.com<mailto:laurent.artusio at orange.com>>
Fecha: miércoles, 18 de septiembre de 2013 11:05
Para: Carlos Ralli Ucendo <ralli at tid.es<mailto:ralli at tid.es>>, "t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>" <t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>>
CC: "fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>" <fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>>
Asunto: RE: [Fiware-iot] IoT Backlog: actions to do

Hello Tarek,

It is normal that you can't directly switch from "under execution" to "closed". There is a workflow to follow.

At first, try to switch from "under execution" to "under verification". After that you should be able to close the tracker.

BR,

Laurent

De : 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] De la part de CARLOS RALLI UCENDO
Envoyé : mercredi 18 septembre 2013 11:00
À : t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>
Cc : fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Objet : Re: [Fiware-iot] IoT Backlog: actions to do

I have forwarded your question to my colleague Manuel to see if he can help you.

Best regards

De: "t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>" <t.elsaleh at surrey.ac.uk<mailto:t.elsaleh at surrey.ac.uk>>
Fecha: miércoles, 18 de septiembre de 2013 10:53
Para: Carlos Ralli Ucendo <ralli at tid.es<mailto:ralli at tid.es>>, "thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>" <thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>>
CC: "fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>" <fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>>
Asunto: FW: IoT Backlog: actions to do

Hello Carlos, All,

For backlog cleaning, I am having a problem changing the "workflow state" for my backlog items that were set for Release 2.3, whereby there are options that are greyed out (i.e. I can't select). For example, if there is an item with "under execution", I cannot change it to "closed".

Is there a reason for this, or somewhere I can refer to for clarification?

By the way, does "closed" mean it is done?

Best regards,
Tarek



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: 11 September 2013 15:08
To: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>
Subject: [Fiware-iot] IoT Backlog: actions to do

Hi all,

Based on the exchange with Manuel, you can find in this new version of the spreadsheet a first sheet with the current architecture of IoT chapter and how we will use the backlog for release 3. So some GE will disappear because we will never use them (Advanced connectivity) but we have to check the related features/epics and workitems to transfer them, if relevant, in another GE. You can find in RED who has to check which "old" GE and in which GE the existing features should go.

We have to provide for October the new deliverable "Backlog" so we have also to clean everything and sometimes also to update the content.

Basically, everything related to R2.3 should be closed because we delivered it in July, and what we could not deliver should now be scheduled (or under execution or closed) in Release 3 In each specific sheet per GE, you have to scroll down to find the list of what is not very well distributed (Release 1, Release 2...), so please take time to update the last topics. We have not so many things to do, thanks to some of you who did a good work before.

For release 3 also I've asked to create name for the instance when we have several instances for the same GE. Typically for Backend Conf Management we should have common features for Orion and IoT Discovery and some should be specific so for the specific ones, you just have now to chose the specific instance. It will be also useful for the workitems and the course to trace that we are preparing content for a specific instance.
This part is more critical for Protocol Adapter because from one protocol to another one, of course we will have specific features.

I have a new check point with Manuel in 2 weeks. The first urgent action point is cleaning the old GEs and if relevant and pushing the features to existing GEs. Second urgent action point: clean old backlogs and populate R3 backlog (consistency with Technical Roadmap).

Thanks for your support.

BR
Thierry

PS: Backend Device Management requests a strong effort because nothing is aligned with IDAS as far as I can check.

_________________________________________________________________________________________________________________________



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.

________________________________

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

_________________________________________________________________________________________________________________________



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.

________________________________

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-iot/attachments/20130918/800f0953/attachment.html>