Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_WIKI_MAINTENANCE_R2, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

Wiki maintenance assures that the wiki is in perfect usable condition.

Task requirements

In this revision the requirements are:

• Delete the obsolete page templates
• Create an iteration page template (see ITERATION_03)
• Review and repair the duplicate information (or at least - start doing it) See implementation idea for this.
• Make sure you've repaired the links in documents that point to a page that you've renamed!
• Add [[BackLinksMenu]] to all of the pages in ImportantDocs

Task result

Maintained wiki.

Implementation idea

Here is a list of pages that contain almost the same (or overlapping) information, missing links, etc.: PROCESS
PLATFORM_INFRASTRUCTURE_OVERVIEW - the repository section should be linked as a part of PLATFORM_STANDARDS_REPOSITORY
PLATFORM_STRUCTURE should be linked in [PLATFORM_STANDARDS_REPOSITORY]
PLATFORM_STANDARDS_NAMING_CONVENTION? - should be discussed with the team leader and filled in with:

• Repository naming convention (don't know where it can be found now
• Wiki naming convention (now part of [PLATFORM_STANDARDS_GENERAL]
• Developers id convention
• Move the naming convention for reports found in REPORTS and link it there
• Move NAMING_CONVENTIONS here
• Move and update UnplannedTasks

This document should be linked where needed.

• TESTING? should be renamed to PLATFORM_STANDARDS_AUTO_TESTS
  • See backlinks and repair the references before renaming!
  • Link testing in PLATFORM_STANDARDS_GENERAL as it is done for analysis and design
• See PLATFORM_STANDARDS_CODE_R0 and rename the resulting pages due to the wiki convention
• Review and remove obsolete information from Important Docs

Related

^{(Here you can add related tasks that could be useful or helpful.)}

How to demo

Show some of the corrected pages and explain the improvements you made.

Design

• Create section with information about holidays in the iteration page (that was added as requirement after the analysis)
  • use table structure
  • mark workdays and holidays
  • write down the important events on their dates (weeklies, progress checks, etc.)
• Remove obsolete page templates
  • See PageTemplates
• Iteration page template content

  == Related Tickets ==
  
  [[TicketQuery(group=status,order=owner,milestone=MILESTONE_NAME,format=table,col=summary|owner|status|type|component|priority|effort|importance)]]
  

• List with pages without [[BackLinksMenu]], linked in ImportantDocs
  • PLATFORM_INFRASTRUCTURE_OVERVIEW
  • PLATFORM_DEPLOYMENT_BUILD_ECLIPSE
  • PLATFORM_STRUCTURE
  • PLATFORM_STANDARDS_GENERAL
  • PLATFORM_STANDARDS_ANALYSIS
  • GLOBAL_SPEC_STRUCTURE
  • JAVADOC_CONVENTIONS
  • NAMING_CONVENTIONS
  • CODE_TASKS_REQUIREMENTS
  • CODE_SMELLS
  • License
• Obsolete pages that must be deleted
  • READ_DOCS? - it is empty and we already keep such record in our internal backlog.
  • SPRINT_LOGS? - it is empty, and the summaries that we're sending in the dev mailist and post in the blog, make this page obsolete.
  • OPEN_QUESTIONS? - it is empty and we already keep such record in our internal backlog.
• Repository documents are now gathered and structured in PLATFORM_STANDARDS_REPOSITORY, that was part of another task
• Remove the overlapping information from PROCESS, PLATFORM_INFRASTRUCTURE_OVERVIEW and etc. if possible (due to the little effort of this revision)
• Creating PLATFORM_STANDARDS_NAMING_CONVENTION? and PLATFORM_STANDARDS_AUTO_TESTS must be included in other tasks, because this has too little effort

Implementation

^{(Implementation results should be described and linked here (from the wiki or the repository))}

Testing

Comments

^{(Write comments for this or later revisions here.)}