Kbase P62094: Bug logging process for ADE and Dynamics bugs.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
Bug logging process for ADE and Dynamics bugs.
GOAL:
How to log bugs for the ADE products.
FIX:
Bug logging process for ADE and Dynamics bugs:
PROGRESS product
All Progress ADE and Dynamics bugs should be logged against the “PROGRESS” product. The “Dynamics” product is closed. Dynamics versions have been added to the “PROGRESS” product and can be entered for a Dynamics bug being logged against the “PROGRESS” product.
All issues migrated to scc from Issuezilla are assigned to the “PROGRESS” product. For fixed bugs, their versions fixed reflect both Progress versions and Dynamics versions in which those bugs were fixed. For example, Issues fixed with the CP31_002_V2B milestone are migrated with versions fixed set to 2.1A,10.0A. For scheduled bugs, their versions to fix reflect both Progress versions and Dynamics versions. For example, Issues assigned to the P31_005_V2BSP1 milestone are migrated with versions to fix set to 2.1A02,10.0A01,10.0B.
When logging a new “PROGRESS” bug, all versions are available to choose on the Which Version pick list. Therefore a bug reported by a customer using the Dynamics product can be logged in scc with “PROGRESS” as the product and the Dynamics version selected from the Which Version pick list. When assigning fixed versions during the triage process, only real Progress versions are available on the Vers To Fix pick list (i.e. 9.1D09, 10.0B, 10.0A01). Dynamics versions are not available on the pick list but can be typed manually and are accepted by the interface after a warning is given.
OEADE dev group
A new development group exists for all ADE/Dynamics bugs, OEADE. The ADE development group is closed. All issues except for briefcase, dictionary and documentation issues migrated to scc are assigned to the OEADE development group. Issues that had been created from scc bugs are updated during migration to be assigned to the OEADE development group. The only bugs remaining with the ADE development group are bugs that existed in scc before posse went live December 2000.
Public vs. private bugs
Internally logged OEADE and DICT bugs are public by default. The short description and public discussion are viewable by the POSSE community. Care must be taken to avoid entering sensitive information into these fields.
The technical description of the bug (e.g. steps to reproduce) must be entered into the public discussion (available by choosing d. Public Discussion) to be available to the POSSE community. Any sensitive information such as customer impact comments or internal company references should be entered into the private description (available by choosing 3.Description and Status).
Component/subcomponents
Components and subcomponents are defined for the OEADE development group. They are organized differently from how the ADE components were organized in scc and how the components and subcomponents were organized on Issuezilla. Many of the scc ADE components were out of date and there were many overlaps between the ADE and Dynamics subcomponents on Issuezilla.
New components have been defined based on functionality of the framework and development environment with minimum overlaps. Most of the components are divided into subcomponents to narrow down the functionality of those components.
The components are:
ADECOMM – Common utilities
BUILD – pbuild
DATABASE – Repository database
Examples of subcomponents are Erwin Integration and Repository Schema.
DEPLOYMT – Deployment services of the framework and development environment. Examples of subcomponents are DCU Upgrade and Installation.
GUIRENDR – Graphical runtime rendering provided by the framework and the Application Development Model (ADM).
Examples of subcomponents are SmartDataObject, Client API and Treeview.
HELP – Framework and development environment help
ICONS – Framework and development environment icons
SERVICES – Services provided by the framework and developmen.t environment. Examples of subcomponents are General Manager, Repository Manager and Session Management.
TOOLS – Tools of the framework and development environment.
Examples of subcomponents are AppBuilder, Container Builder, SCM Integration and TranMan.
WEBRENDR – Web runtime rendering provided by the framework.
Dynamics Web is currently the only subcomponent; this will be expanded.
WEBSPEED – Webspeed runtime rendering and development tools.
Subcomponents are WebSpeed Rendering and WebTools..