Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • O org.eclipse.dash.handbook
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 156
    • Issues 156
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Technology
  • Eclipse Dash
  • org.eclipse.dash.handbook
  • Issues
  • #80
Closed
Open
Issue created Sep 22, 2017 by Eclipse Webmaster@webmasterOwner

Describe the life-cycle of the bugs we create to track project creations and reviews.

Submitted by Wayne Beaton @wbeaton

Link to original bug (#522675)

Description

The Eclipse Projects Team creates the bug for tracking our processes; we'll close it.

We keep the proposal/creation bug open until after the project has done it's first release.

Review tracking bugs are closed when the review is declared successful and activities related to the review have been completed. For release reviews, the bug is closed immediately after success is declared. For restructuring and termination reviews, we keep the bug open until the related activites (e.g. archiving a project) are complete.

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent