| Summary: | Release Notes reports "Error: could not connect to database!" | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Alexander Nyßen <nyssen> |
| Component: | Website / Wiki | Assignee: | gef-inbox <gef-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, irbull |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 363394 | ||
| Bug Blocks: | |||
|
Description
Alexander Nyßen
Augmented relnotes.php with information about new releases: $streams = array( "gef" => array( "3.7.x" => "HEAD", "3.6.x" => "R3_6_maintenance", "3.5.x" => "R3_5_maintenance", "3.4.x" => "R3_4_maintenance", "3.3.x" => "R33_maintenance", "3.2.x" => "R32_maintenance", "3.1.x" => "R31_maintenance", "3.0.x" => "R30_maintenance" ), ); However, the db connection problem is still an issue. The modeling projects seem to have the same problems, e.g. compare http://www.eclipse.org/modeling/emf/news/relnotes.php?project=emf&version=HEAD The release notes were generated by the integration in the Common Modeling Build that GEF and some of the modeling projects use. Nobody is maintaining the Common Modeling Build anymore, we were supposed to either move to Athena, Buckminster or something else. The modeling projects are supposed to move to Buckminster and Ian said he would do this work for GEF. With regards to the Release Notes being broken for GEF, the release notes were a list of Bugzillas resolved in that particular build. We currently have no idea what is fixed in a particular build and when you check a bugzilla and ask when build has the fix, there is no obvious answer. As this is no longer directly referenced on the GEF main page (but only from the downloads page), reducing severity. (In reply to comment #4) > As this is no longer directly referenced on the GEF main page (but only from > the downloads page), reducing severity. As soon as the changes I applied to the build pages under bug #363394 are live, we can regard this as being resolved. As the old webpages have been replaced, as documented in bug #363394, this no longer holds. |