Dear all,
I added the topic to the minutes for the confcall ...
I support the idea to provide support on the last available version,
assuming that the migration procedure (for software, configuration and
data) is properly described (and tested).
Manuals (installation, admin, users) for the old versions can be kept in
the wiki as useful resources for who is still using those versions, but
without official support.
BR
Davide
2014-10-05 10:20 GMT+02:00 Juanjo Hierro <juanjose.hierro at telefonica.com>:
>
> Let's try to discuss this in our weekly confcall, please add this point
> as item in the agenda.
>
> In the meantime, I would encourage you to make a proposal.
>
> I tend to think we should just provide support of the latest version:
>
> - Regarding most of the GEris of the Data/Media Context Management
> chapter, it shouldn't be a big deal to ask users to update the version of
> the GEris they are using to the most recent version because such updates
> shouldn't be so difficult to install and configure. Probably the only
> exception would be the BigData GEri, with which I believe that support of
> versions is very much tied to the support of the underlying technology
> (Hadoop).
> - Regarding most of the GEris of the IoT Services Enablement, the
> Advanced Web-based UI and the Apps/Data delivery chapters, I believe that
> similar argument may apply, but I would like to hear Thierry/Carlos,
> Philipp, and Alessandra/Javier, respectively. Regarding the Apps/Data
> Delivery chapter I believe that most users should try to experiment with
> GEris deployed globally on FIWARE Lab and used "as a Service" and we should
> recommend that (remember the note we asked them to incorporate in entries
> of the Catalogue), therefore I would say that we should just support the
> version that is offered globally as a Service, even for local deployments.
> - Regarding GEris of the Cloud, Security and I2ND (network) chapters,
> which are more kind of "infrastructure" GEris, I believe that we should
> encourage usage of what is on the FIWARE Lab and we should just support the
> versions of what is supported there as part of the infrastructure
> - Regarding GEris linked to the middleware (KIARA) and robotics in the
> I2ND chapter, which are not yet available I believe that the same reasoning
> as with GEris of the Data/Media Context Management should apply but I would
> like to hear Pier/Thomas.
>
> Given said the above, I believe that we should document these policies
> in the entries of the FIWARE Catalogue corresponding to each FIWARE GEri.
> Probably adding a new tab on the matter ("Support" ?)
>
> Let's add this as an item on the agenda of our Monday meeting and
> discuss this offline in the meantime.
>
> Best regards,
>
> -- Juanjo
>
> -------------
> Telefonica - Product Development and Innovation (PDI)
> website: www.tid.es
> email: juanjose.hierro at telefonica.com
> twitter: twitter.com/JuanjoHierro
>
> FI-WARE (European Future Internet Core Platform) Coordinator
> and Chief Architect
>
> You can follow FI-WARE at:
> website: http://www.fi-ware.org
> facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
> twitter: http://twitter.com/FIware
> linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
>
> On 05/10/14 08:59, Alex Glikson wrote:
>
> Dear Juanjo, all,
>
> While this is definitely a step in the right direction, I think we need to
> clarify the exact impact on the GEi users.
> More specifically, do we need to maintain proper versions of the GEis?
> Should users be able to download & install older versions? Do we need to
> *support* older versions? For how long? How about documentation associated
> with older versions? What should be the approach wrt upgrades and
> backwards-compatibility? Would it be different for different GEis, or
> different groups of GEis? (e.g., global instances versus those installed
> manually versus those installed via Cloud tools)
> These questions will be critical as more people start using our GEis.
>
> Thanks,
> Alex
>
>
> ====================================================================================
> Alex Glikson
> Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab
> Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile:
> +972-54-6466667 | Fax: +972-4-8296112
>
>
>
>
>
> From: Juanjo Hierro <juanjose.hierro at telefonica.com>
> <juanjose.hierro at telefonica.com>
> To: "fiware at lists.fi-ware.eu" <fiware at lists.fi-ware.eu>
> <fiware at lists.fi-ware.eu> <fiware at lists.fi-ware.eu>,
> <fiware-chapter-architects at lists.fi-ware.org>
> <fiware-chapter-architects at lists.fi-ware.org>,
> <fiware-chapter-leaders at lists.fi-ware.org>
> <fiware-chapter-leaders at lists.fi-ware.org>
> Date: 03/10/2014 09:00 AM
> Subject: [Fiware-chapter-leaders] Synchronizing all the GEri
> related materials
> Sent by: fiware-chapter-leaders-bounces at lists.fi-ware.org
> ------------------------------
>
>
>
> Dear all,
>
> It seems that our repositories are not always well aligned and part of
> this is caused by the lack of flexibility in the procedures. We have
> decided to give it a push by relaxing the current work procedure.
>
> This was triggered by finding that some partners have new versions of
> code (R3.4 , for instance) and the manuals were the old ones for R3.3.
>
> Those partners with GEris to be published on the catalogue (those on [1])
> must ensure consistency with the latest release delivered:
>
> - Ensure that the latest version is available in a repository clearly
> linked from the catalogue in the Downloads tab(Files, github or whatever
> you use)
> - Update the Installation and admin manual on the public wiki directly
> and make sure that it is referred from the catalogue
> - Update the User & Programmer manual on the public wiki directly and
> make sure that it is referred from the catalogue
> - Update the Unit Testing Plan manual on the public wiki directly and
> make sure that it is referred from the catalogue
> - Update the FIWARE Lab recipes, images, etc. if needed
> - Update the FIWARE Academy courses (*http://edu.fi-ware.org/*
> <http://edu.fi-ware.org/>) if needed
>
>
> The only step on which we will keep applying supervision is publication
> of VM images, deployment recipes, etc. on FIWARE Lab.
>
> The catalogue has a workflow that still implies approvals of edited
> entries but Stefano will try to swiftly approve your edits until we
> implement a more agile workflow (under definition).
>
> From now on, updating the software means updating everything and keeping
> it in perfect synchrony. It can be done anytime, at the end of every Sprint
> or even in its middle (e.g., due to a hot patch it is urgent to publish).
> The manuals and info must correspond to the same release always. To avoid
> temporary inconsistencies, we ask you to prepare everything offline in the
> most suitable repository in each case(word, private wiki, etc.) and port it
> all in one go to the all the repositories.
>
> The Security chapter is still backdated (in R2) and R3 will be ported to
> the public wiki by Thales shortly. You will have to internally coordinate
> in Security to publish all your stuff in an orderly fashion.
>
> Note that with all these measures we are giving you a lot of empowerment.
> We will implement a methodology that will mean that such empowerment will
> remain for those partners who show they are reliable. However, a given
> FIWARE GEri owner or even a complete chapter may loose this empowerment and
> it will be put in quarantine (i.e., activities under close supervision and
> strict approval procedures) if it is find out that general rules,
> templates, etc are not followed or provided content is not of enough good
> quality.
>
> Best regards,
>
> Miguel and Juanjo
>
>
> [1]
> *https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdG83Y0dQVEFKSHFYWmtXdlpEdnVpaXc&usp=sharing#gid=0*
> <https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdG83Y0dQVEFKSHFYWmtXdlpEdnVpaXc&usp=sharing#gid=0>
>
>
>
>
> ------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
> _______________________________________________
> Fiware-chapter-leaders mailing list
> Fiware-chapter-leaders at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-chapter-leaders
>
>
>
> ------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
>
> _______________________________________________
> Fiware-chapter-leaders mailing list
> Fiware-chapter-leaders at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-chapter-leaders
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-chapter-leaders/attachments/20141006/72d0d3ac/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy