[Fiware] Source code and binary packages releasing procedure for FI-WARE Release 2

Fermín Galán Márquez fermin at tid.es
Tue Feb 5 16:54:20 CET 2013


Dear Henk,

Yes, we understand that this kind of software is highly depended of the
hardware platform in which it runs. However, although it could be not
useful to release it as binary form (source code form releasing could be
useful, but it is not mandatory) this kind of software must also be
released following the rules in
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware,
in order to make the process homogeneous along the project and, probably
most important, to avoid misunderstanding with the EC (they are
expecting that we release each GEi on the GEi list).

I hope have clarified your doubt. Don't hesitate to contact us again if
you need.

Best regards,

------
Fermín


El 05/02/2013 16:24, Heijnen Henk escribió:
> Hello,
>
> What about software targeting embedded platforms instead of servers ? (for example the Cloud Proxy: it runs only on a dedicated HW that is proprietary)
>
> Same problem with most of the I2ND GEs and (maybe) some IoT ones ...
>
> Regards
> Henk
>
>
>
> Henk  HEIJNEN
> Manager, Cooperative Projects
>
> Research & Innovation
> Funded & Cooperative Programs
> 975 avenue des champs blancs - CS 17616
> 35576 Cesson-Sévigné cedex - FRANCE
> Tél:  +33 2 99 27 33 08 -  GSM: +33 6 72 39 26 24 - BU4/114
>
>
>
> -----Original Message-----
> From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of Fermín Galán Márquez
> Sent: mardi 5 février 2013 16:21
> To: fiware at lists.fi-ware.eu
> Subject: [Fiware] Source code and binary packages releasing procedure for FI-WARE Release 2
>
> Hi,
>
> We have defined a guide on how to release source code and binary
> packages for FI-WARE release 2 and beyond, that can be found at:
>
> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware
>
>
> (It is also linked from the Handbooks section in the FIWARE wiki main page)
>
> This is the procedure that each GEi implementor must  follow when
> releasing the software for Release 2. Although it will be at that time
> when you will need to follow it, we think a good idea to publish it in
> the wiki and send this email at the present moment so you can know it in
> advance and even use it for releasing any GEi release between now and
> Release 2 if you want.
>
> We used SCM (i.e. Subversion) in the previous release due to problems
> with the "Files" tool on the forge that are solved now. The old delivery
> of Release 1 can stay as it is (there's no need to migrate) but the next
> ones will use the "Files" part of the forge, that is more adequate for
> our needs and  gives a better impression, especially towards external
> developers communities.
>
> Please, don't hesitate to contact me if you have any doubt or comment.
>
> Thanks!
>
> Best regards,
>
> ------
> Fermín
>
> ________________________________
>
> 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 mailing list
> Fiware at lists.fi-ware.eu
> http://lists.fi-ware.eu/listinfo/fiware


________________________________

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



More information about the Old-Fiware mailing list

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