Opened 13 years ago

Closed 13 years ago

#64 closed task (fixed)

Document testing, reporting, and ticketing procedure

Reported by: andersd Owned by: EliL
Priority: major Milestone:
Component: Docs Version:
Keywords: website, testing, tickets Cc:

Description (last modified by EliL)

Users need to know how to test and report on their results. That needs to be documented. This is particularly the case when a release is coming soon. Some suggestions have already been sent offline.

Change History (4)

comment:1 by EliL, 13 years ago

Description: modified (diff)
Owner: changed from andersd to EliL
Reporter: changed from EliL to andersd
Status: new → assigned

comment:3 by andersd, 13 years ago

What's new in 2.6?

Standard Installation

  1. LINUX
  2. ms4w - Apache

Standard Customization

  1. Map Page Customization
  • a.Updating the page style "skin"
  • b. Add calls to your site
  1. Customize for your data
  • a. Zoom To
  • b. Map Extent
  • c. Making map files
  • d. Adding map files
  • e. Customizing the Catelog
  1. Customizing services
  • a. Identify Service
  • b. Select Service
  • c. Search Seavice
  1. Customize Tool Bars
  1. Update printing
  • printing maps
  • printing lists
  1. Customizing the Locator Map

Advanced Customization

  1. Removing services
  2. Adding services

comment:4 by andersd, 13 years ago

Resolution: → fixed
Status: accepted → closed

The previous stuff was put in the wrong place. It should be in #57.

Note: See TracTickets for help on using tickets.