[Fiware-miwi] historic open items in tracker and naming conventions

[Toni Alatalo]

I think that is what I said :)

That is, in the tracker’s alternative reality the work we are doing today is in December, in sprint 3.2.something, for release 3.2 which is coming out now.

If we do some work now which we don’t release next week then we can put that to sprint 3.3.1 I think. But most of the January work we are releasing next week.

Thanks for the clarification, I’ll change — that’s how I had those originally but got confused then yesterday evening when we looked at the official schedule in the wiki with Lasse (I think we had the same misconception untill now).

~Toni

On 24 Jan 2014, at 14:06, Christof Marti <mach at zhaw.ch> wrote:

> Hi Toni
> 
> No, we are already in Release 3.3 phase. Release 3.2 was due in December.
> All work items for sprint 3.3.1 should also have Relese 3.3 assigned.
> Features and items for R3.2 should be closed  or „Finished but not released“.
> The software we are releasing now is the one officially developed until end of December (R3.2)
> Next release will be 3.3 (in March).
> 
> 
> Christof
> 
> Am 24.01.2014 um 12:56 schrieb Toni Alatalo <toni at playsign.net>:
> 
>> On 24 Jan 2014, at 12:48, MANUEL ESCRICHE VICENTE <mev at tid.es> wrote:
>>> Please, let me a note on this sentence:
>>> "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned"
>>> ->Features hold only as time frame Release
>>> ->Stories, Bugs and WorkItems hold both Release and Sprint
>>> ->Epics don't hold any timeframe
>> 
>> Ok thanks for info, I think at least I've got these largely wrong because:
>> 
>> current sprint is 3.3.1, right?
>> 
>> upcoming release is 3.2, right?
>> 
>> so the work we are currently doing is in 3.3.1 and coming out in release 3.2.
>> 
>> but we should not mark it in the tracker like that but put also current activities for this release for the December sprint?
>> 
>> I can change these when get a confirmation.
>> 
>> ~Toni
>> 
>>> -----Original Message-----
>>> From: Christof Marti [mailto:mach at zhaw.ch]
>>> Sent: viernes, 24 de enero de 2014 11:26
>>> To: FI-WARE, MiWi
>>> Cc: MANUEL ESCRICHE VICENTE
>>> Subject: historic open items in tracker and naming conventions
>>> 
>>> Dear WP13 GE owners
>>> 
>>> I was checking the tracker and still found some errors and naming inconistencies.
>>> 
>>> There are still some historic entries, which are not closed or „Finished but not released“.
>>> Historic means belong to Release 3.2 (which ended in December).
>>> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse
>>> I created a specific advanced query for these entries named "All historic open“.
>>> 
>>> All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned.
>>> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description.
>>> (e.g. with the line „Deliverable = D.13.3.3“)
>>> 
>>> List of actual deliverables:
>>> D.13.1.2 GE Open Specificatoin (M30)
>>> D.13.1.3 GE Open Specification (M33 or M36)
>>> D.13.2.3 GE SW Release (M33)
>>> D.13.3.3 GE Installation and Administration Guide (M33)
>>> D.13.4.3 GE User and Programmer Guide (M33)
>>> D.13.5.3 GE Unit Testing Plan & Report (M33)
>>> D.2.3.3  FI-WARE Architecture V3 (M33)
>>> D.2.4.3  FI-WARE Technical Roadmap V3 (M33)
>>> 
>>> Please also check the naming patterns:
>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use
>>> Specially also add the „action“ extension at the end.
>>> 
>>> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example:
>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3)
>>> 
>>> or for update of the Architecture of the 3D-UI GE:
>>> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3)
>>> 
>>> or for creating the SW package:
>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver
>>> 
>>> Watch also the difference between the GE naming „3D-UI“ and the GEi naming „3D-UI-WebTundra“ resp. "3D-UI-XML3D (only required if more then one implementation is available).
>>> 
>>> Naming conventions for Features, UserStories etc can be found here:
>>> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow)
>>> 
>>> Cheers
>>> Christof
>>> ----
>>> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering
>>> Phone: +41 58 934 70 63
>>> Skype: christof-marti
>>> 
>>> ________________________________
>>> 
>>> 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-miwi mailing list
>>> Fiware-miwi at lists.fi-ware.eu
>>> https://lists.fi-ware.eu/listinfo/fiware-miwi
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140124/b3f4d8fe/attachment.html>