Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 359283

Summary: Migrate Commits Explorer to Git
Product: [Technology] Dash Reporter: Wayne Beaton <wayne.beaton>
Component: Commits Explorer (Retired)Assignee: Project Dash Incoming bugs <dash-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: sbouchet
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on:    
Bug Blocks: 358980    

Description Wayne Beaton CLA 2011-09-28 13:43:40 EDT
Time to migrate.
Comment 1 Eclipse Webmaster CLA 2014-01-28 13:07:02 EST
Wayne you've finished this right?

-M.
Comment 2 Wayne Beaton CLA 2014-01-29 14:30:59 EST
(In reply to Eclipse Webmaster from comment #1)
> Wayne you've finished this right?

Yup.
Comment 3 Bouchet Stéphane CLA 2014-01-30 03:20:16 EST
Humm,

this is a minor change, but the main page of dash.eclipse.org[1] still display "Explore the "commits to the source code (CVS and SVN) repositories" for all the Eclipse projects." for commits explorer.

Maybe a little  modification is necessary ? 

Cheers,

[1]http://dash.eclipse.org/dash/commits/web-app/
Comment 4 Eclipse Genie CLA 2016-01-21 06:07:47 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Bouchet Stéphane CLA 2016-01-21 07:36:23 EST
I think this bug can be closed, the new dashboard is now operationnal and there is a direct link on it on the old dash.
Comment 6 Wayne Beaton CLA 2016-01-21 11:10:24 EST
I updated the website content (for completeness). It appears, however, that the existing site hasn't been updated since we switched from CVS to Git and so the process for issuing updates is broken. I don't consider this update critical and so consider pushing the update to the website low priority. At some point, it'll get pushed out as part of another update (or not).