Hi all, Davide has kindly mentioned: "The REPAIR MANUAL tracks also the change of the entry type in the entry name of the backlog items and wiki entries. But this is a T-C2 issue, that I intended being not urnet ones: "For priority, tracker metrics T-C1 and T-C2 can be currently neglected if you want to spare some efforts now, but it will be checked sometimes later (Manuel said he would be able to automate the fixes to these detected issues.)"" Thank you so far, I have not recognized this in my mail from yesterday that we also have addressed T-C2 in the repair manual (my mistake). I do not know for this T-C2 if Manuel can automate this in the future. But I would rather not wait for this - given that we have (relatively) few issues here to handle and the automation plans from Manuel seem to be around for a while now if I am informed right. So I would recommend to just carry out these steps (included in the manual) to get many issues closed in one chunk and get rid of this task. More in general, my overall recommendation would be to close all / as many-as-possible of the listed issues for the GEs simply. The manual is just a sort of help/motivation there and you can work on the issues freely. We from SAP did this now for these issues and hope that we catched all or many of these issues now finally --> this said as a motivation who wants to be second hehe :) Best wishes Markus From: markus.heller at sap.com Sent: Montag, 30. September 2013 18:08 To: 'fiware-apps at lists.fi-ware.eu' Subject: Fixing backlog: Tracker, Wiki, Roadmap, Unit Test Plans --> Repair Manual Hi all, Last week I had my telco with Manuel about the WP3 backlog status, our progress was not too good. I would like to mail the following summary and a new manual to fix these resources. As you might know, I know about the efforts (we in SAP carried it out already...) but I can only ask you to carry this out. Please see that maybe coordinator can evaluate these resources and use them for reporting progress etc. I have added the latest XLS as attachment that I will use as a master here in this mail (w.r.t line numbers, for example). Important: Some of you have repaired these issues already, so the issues reported here may be outdated for your own GEs now, you know best what is open or fixed. I have no newer XLS version currently. As a result of the telco, the main focus for our fixed should now be (only, as negotiated) on (a) "hierarchy / parent & child entries" and (b) consistency Tracker/WIKI/Roadmap/UTP's. We would need to fix the following issues: a) Tracker T-C3: Not all areas, only lines 5-19 (=15 entries here) and lines 29-170 (=142 entries here) b) Tracker T-C4: Not all areas, only lines 106-143 (48 entries there) c) Wiki W-C0: Not all areas, only lines 4-43 (=40 items here) To fix these issues, we have attached a repair manual below that will help fixing the bugs in steps a), b), c) above or just choose your own approach. Notes: - This immediate team focus on the Hierarchy Issues would bring our "Apps Chapter" immediately into a very comfortable Tracker Clean State. Therefore Manuel urged to concentrate on this, I would support this since with a rather moderate effort (compared to some other WP's) we have the chance to close this topic once and for all. My former own opinion was that we might be able to only focus on Hierarchy Issues for the _future_ sprints/releases. I (had to) change this opinion and I considered it moderate effort before in my last mails, compared to other WP efforts (although not a best-one argument I admit...). So now focus would be on both sprints/releases in the _past_ and the future (some of you already did fix this anyway). - For priority, tracker metrics T-C1 and T-C2 can be currently neglected if you want to spare some efforts now, but it will be checked sometimes later (Manuel said he would be able to automate the fixes to these detected issues. - Important: You have to be very cautious with your modifications in WIKI, Tracker, Technical Roadmap, Unit Test Plans because some deliverables are derived/generated from this material. If your links remain in a "bad" after your fixes, your work might NOT END UP in the deliverables !! Deadline: In any case, please fix the issues asap (release 2 closure). The fixes target Release 2 and Release 3. Best wishes Markus --- REPAIR MANUAL to fix the resources (if you detect errors, please mail your corrections to ALL in FI-WARE Apps): (Kudos for Andreas Klein for this manual!) A. WIKI & TRACKER UPDATES 1. For all your Epics: a. In WIKI, replace "EPIC" with "Epic" in the Epic-Identifier (Example old: "FIWARE.EPIC.Apps.Marketplace.RatingAndFeedback<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Apps.Marketplace.RatingAndFeedback>" to new "FIWARE.Epic.Apps.Marketplace.RatingAndFeedback<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.Apps.Marketplace.RatingAndFeedback>" b. In WIKI, move the old WIKI page (because page title is wrong: EPIC --> Epic). Use "MOVE" command of the WIKI (not manually...) c. In Tracker, replace "EPIC" with "Epic" in the Epic-Identifier (similar to 1.a.) d. In Tracker, correct the Link URL to the WIKI page resulting from step 1.b. 2. For all features a. In WIKI, replace "FEATURE" with "Feature" & insert Epic-Name (= the parent epic of this feature) in the Epic-Identifier (Example old: "FIWARE.FEATURE.Apps.Marketplace.RecommendedSimilarUsers<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers>" to new "FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers> " b. In WIKI, move the old WIKI page (because page title is wrong): (Example old page name: "FIWARE.FEATURE.Apps.Marketplace.RecommendedSimilarUsers<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers>" to new page name "FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers> " Use "MOVE" command of the WIKI (not manually...) c. In Tracker, replace "FEATURE" with "Feature" & insert Epic-Name (= the parent epic of this feature) in the Feature-Identifier (similar to 2.a.) d. In Tracker, correct the Link URL to the WIKI page resulting from step 2.b. 3. For all stories a. For Stories, we do not have stories in the WIKI, so no WIKI modifications here. b. In Tracker, replace "STORY" with "Story" & insert Feature-Name (= the parent feature of this story) in the Story-Identifier (Example: old "FIWARE.STORY.Apps.Marketplace.RecommendedSimilarUsers<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=4899&group_id=12&atid=181>" to new "FIWARE.Story.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=4899&group_id=12&atid=181>) c. In Tracker, make sure that NO LINK (must not be there) exists to the WIKI page resulting from step 2.b. B. Technical Roadmap 4. In Technical Roadmap Page, the links to Epics, features, Stories now do not point to the new WIKI Pages now, they are "broken": For all Epics, Features, Stories: Correct all URLS so that they point to the new WIKI pages. C. Unit Test Plans 5. In Unit Test Plans, the links to Epics, features, Stories now do not point to the new WIKI Pages now, they are "broken": For all Epics, Features, Stories: Correct all URLS so that they point to the new WIKI pages. Best wishes Markus From: markus.heller at sap.com<mailto:markus.heller at sap.com> Sent: Donnerstag, 19. September 2013 11:49 To: 'fiware-apps at lists.fi-ware.eu' Subject: FW: Roadmap and backlog reviews Hi WP3, Please, find below links to reviews done over the trackers ...and overall we/I have following dates set by Manuel: · WPL review meeting - Scheduled next week (24-30 Sept) for reviewing the backlog status. · Backlog - Has a delivery scheduled by 30th October. · Roadmap - Next sprint planning meeting will consider R3 roadmap. These meeting will be held by 7-11 October. WP3-Apps(@Markus) https://forge.fi-ware.eu/docman/view.php/27/2817/FIWARE.backlog.apps.review.20130918-1831.xlsx Progress from last report (Tracker:69.8%->69.2%; Flat structure:89.9%->87.2%; Wiki:18,9%->19.6%) "Markus, Indicators show little progress, but some on Tracker and Structure. Please, have a look at WP6, which has shown progress is possible on Structure, they started with 94% and have progressed to 36%" @ALL: Please grab a cup of coffee and fix most of your open items here (not necessarily the issues with only informative character, just leaver them for now), but the important ones where CONSISTENCY is broken or content is wrong/missed and in non-agreed format. Please just fix this so that we can get rid of it and not always get these back. I know of some on-going discussions if something is really needed or has changed since then sometimes and for many items (mostly relevant in other chapters, not ours). But: Most of us in OUR WP3 do not need to do much, I guess all is done in less than 30 minutes for most issue types - and then it would be over. For example clicking consistency between FORGE and WIKI is really good to have fixed, similar applies for the others. If in doubt, ask me. Especially For issue type "flat structure": I advise this compromise as discussed with Manuel: - R3 and higher: Please introduce the necessary hierarchiy in the tetnries that you created for R3 and beyond. In many cases you created only features, but not always the necessary parent elements or vice versa. Please fix this. - Lower than R3: For now, fixing hierarchy for backward release is - for those GEs with MANY entries - also requested as well from you but lesser priority. Of course, in the cases where for YOUR GE there is NOT much to do to get this to zero, please simply fix the stuff so that we can get rid of it and complete these open issues. This is not much of your time and makes life easier for Manuel and us. Please come back to me with any wquestions and please fix this with Deadline: Tuesday EOB Best wishes Markus -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20131001/081909c4/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy