[Fiware-data] Issues with software release in WP6

Marti Christof (mach) mach at zhaw.ch
Tue Apr 23 17:34:33 CEST 2013


Hi Fermin, Sergio

I fixed the release numbering of the DATA-Middleware.

Best regards
Christof

Am 23.04.2013 um 13:33 schrieb Fermín Galán Márquez <fermin at tid.es<mailto:fermin at tid.es>>
:

Hi,

(This email is addressed to Data Chapter WPL, but given he is off due to local holiday and this is an urgent issue, I'm CCing the whole chapter. Sorry for the inconveniences this may cause).

I'm checking the sw release of WP6 and I have seen the following GEis are missing:

  *   LOCS
  *   Semantic Application Support

In addition, I found some issues with GEis actually released:

  *   According to https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware#Release_Management<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware#Package_Management>: "Naming convention: use X.Y.Z format". In the "DATA-Middleware" release you use "R2.2", which is not right. Change if to "2.2" (without "R").

We are now beyond deadline (it was April 22nd) so, please solve the above issues as soon as possible.

Thank you very much!

Best regards,

------
Fermín

PD. My check is based in information gathered at 12:30 today.


El 15/04/2013 17:15, Fermín Galán Márquez escribió:
Hi,

As far as I understand, the following GEis from WP6 are included in the April release:

  *   Complex Event Processing
  *   Compressed Domain Video Analysis
  *   Media-enhanced Query Broker
  *   Location Platform
  *   Semantic Application Support
  *   Meta-data Pre-processing
  *   Middleware

However, as far as I have checked in FI-WARE PPP Restricted Files (https://forge.fi-ware.eu/frs/?group_id=23) and FI-WARE Files (https://forge.fi-ware.eu/frs/?group_id=7), none of them has been yet released. Note that although there is a DATA-CEP package in https://forge.fi-ware.eu/frs/?group_id=23 it has "No releases".

Given that the deadline for the release (April 22nd) is only one week ahead we wonder if you WP will be able to release them on time. As WPL/WPA, could you tell me the status of the releasing process within your WP, please?

Thanks!

Best regards,
------
Fermín

PD. For your convenience, this is the link to the releasing procedure to follow: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Tutorial_releasing_fiware


-------- Mensaje original --------
Asunto:         [Fiware] Guidelines for Release 2
Fecha:  Thu, 28 Mar 2013 02:24:26 +0100
De:     Miguel Carrillo <mcp at tid.es><mailto:mcp at tid.es>
Responder a:    <mcp at tid.es><mailto:mcp at tid.es>
Organización:   Miguel Carrillo
Para:   fiware at lists.fi-ware.eu<mailto:fiware at lists.fi-ware.eu> <fiware at lists.fi-ware.eu><mailto:fiware at lists.fi-ware.eu>


Dear all,

Given the importance of the general guidelines for the delivery of the deliverables associated to the software and the absence of key components of the team due to the Easter holidays, this message is directly sent to all the consortium. Be ready for a long but extremely important message.

This is strictly about :

  *   Delivery of the Software itself
  *   Installation and Administration manual
  *   User and Programmer manual
  *   Unit Testing Plan and report

The date for delivery to the EC is the end of April so we will need to have all complete and ready for review by April, 22 , as agreed in the past WPL/WPA call.

The guidelines are available on the private wiki (if you do not have access, ask your WPL or WPA to fix it) . The link to the detailed guidelines  is here(you need to this them before editing the deliverables):

  *   https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR2

Please note that:

  *   The guidelines  for the docs are basically the same ones as for Release 1
  *   The guidelines for the software delivery are completely different and were sent by Fermín to this list ages ago

Please use the placeholders to edit each document (linked from the guidelines page). Most of the chapters have not started this work, they must use the private wiki following the links under the placeholder section in the guidelines. Exceptionally, if someone has started editing the changes somewhere else (I am only aware of some GEs in WP3), carry on working there but this place must be linked from the placeholders, so make them point at the right location where you actually work . If you start working now you must use the links provided and the private wiki.  I will ask to revert any unauthorised changes in the public wiki, I insist that you must use the private wiki (the public wiki should only have definite manuals, not intermediate stuff).

Be aware that this time moving pages across different wikis (figures included) is done in a matter of seconds thanks to a tool developed by SAP. Your WPL must have access to it (or can ask for access to it if he has not done so yet)

  *   This will ease the work of copying the definite versions of the manuals to their final destinations.
  *   Also, if you need to use a previous version on the manual as the basis for the coming issue of the docs, this   tool can be used to take a copy of the current wiki pages to the private wiki prior to the start of your work.

Check with your WPL/WPA if you have any doubts, I will only answer queries routed via the WPL/WPAs to ensure a good synchronisation of the whole process.

Best regards,

Miguel


________________________________

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-data mailing list
Fiware-data at lists.fi-ware.eu<mailto:Fiware-data at lists.fi-ware.eu>
https://lists.fi-ware.eu/listinfo/fiware-data




More information about the Old-Fiware-data mailing list

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