Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 154
    • Issues 154
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • 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 Projects
  • Eclipse Dash
  • org.eclipse.dash.handbook
  • Issues
  • #6

Closed
Open
Created Aug 20, 2015 by Eclipse Webmaster@webmasterOwner

Move Project Handbook source to Dash

Submitted by Wayne Beaton @wbeaton

Assigned to Wayne Beaton @wbeaton

Link to original bug (#475496)

Description

I created the handbook source in the /projects directory directly. I did this primarily out of convenience so that I could focus on content. Now that I've completed the first version of the handbook, I'd like to extract the source from /projects and put it into its own dedicated repository. I'd like that repository to be connected into Gerrit.

I believe that moving it to Dash makes sense. I believe that the handbook reasonably qualifies as a tool for committers, so it is in-scope. The handbook source can be moved into its own repository and easily connected to Gerrit. Further, by having it in a project, we can request a Hudson instance to provide some CI functionality.

In these early days, it's been convenient to be able to push out regular minor updates, but now that we've reached a level of maturity, it makes sense to start treating the handbook like an actual project and schedule actual releases. i.e. conform to the development process.

Actual release content will be pushed into the /project directory (where it currently resides).

Blocking

  • Bug 482414
Assignee
Assign to
Time tracking

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