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

Bug 310961

Summary: 3.6M6 Build is incorrectly labeled as 2.6M6 on project page.
Product: [Tools] GEF Reporter: Alexander Nyßen <nyssen>
Component: Website / WikiAssignee: Anthony Hunter <ahunter.eclipse>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: ahunter.eclipse
Version: 3.6   
Target Milestone: 3.6.0 (Helios) RC2   
Hardware: All   
OS: All   
Whiteboard:

Description Alexander Nyßen CLA 2010-04-29 03:12:32 EDT
On the GEF project page (http://www.eclipse.org/gef/), within the build news section, the latest build is listed as 2.6M6.
Comment 1 Anthony Hunter CLA 2010-04-29 09:35:12 EDT
This was a promote mistake I made, I thought I fixed everywhere but there are a few places:
/cvsroot/org.eclipse/www/gef/feeds/builds-gef.xml
/cvsroot/org.eclipse/www/gef/updates/milestones/site-helios.xml
/cvsroot/org.eclipse/www/gef/updates/milestones/site.xml
Comment 2 Anthony Hunter CLA 2010-04-29 09:40:16 EDT
Fixed,

I did the manual cvs update -R on the build machine. The GEF project web site should refresh in the next two hours.
Comment 3 Alexander Nyßen CLA 2010-05-02 09:35:06 EDT
Well, it does not seem as if this has resolved the issue. The build news still specify 2.6M6 and the same holds for the build page.
Comment 4 Anthony Hunter CLA 2010-05-03 13:06:01 EDT
sigh, well http://www.eclipse.org/gef/feeds/builds-gef.xml says 3.6.0M6.

A second interesting note is that nothing past 3.6.0M6 and March 15 is there.

I did raise Bug 301742 about the issue with the feeds.
Comment 5 Anthony Hunter CLA 2010-05-17 15:16:42 EDT
This is not going to be looked at today, so moving off the RC1 target milestone.
Comment 6 Alexander Nyßen CLA 2010-05-19 08:40:50 EDT
From what I could infer from the modeling-www php scrips, the data is extracted from a mysql database, which was not updated.
Comment 7 Alexander Nyßen CLA 2010-07-20 18:07:42 EDT
While this is not resolved properly, I think we can regard it as a wontfix, as a milestone build is not likely to be searched and consumed after the 3.6 release has been out.