Bugzilla – Full Text Bug Listing
| Summary: | Improve some of our simple "extra info" download pages | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> |
| Component: | Releng | Assignee: | Platform-Releng-Inbox <platform-releng-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | akurtakov |
| Version: | 4.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
David Williams
Changing title to this bug can track a number of small improvements, one of which is "wrap in standard Eclipse (Nova) theme" Another small improvement, Where we currently say: View the repositories used for the current build. Would probably better be labeled as Repositories, branches, and tags used for current build. Once we wrap "repositories used for the current build" with enough PHP to produce simple Nova theme, we could also enhance the information there to include EMF repo used: ECF repo used: Orbit repo used: then see eclipse-sdk-prereqs.target for more details ... which, also implies we make a copy of that to our download page (it would also need to be "wrappped" for theming. (and, perhaps point to instructions on how to use "PDE runtime targets). We could also include a pointers to our more elaborate "reverse look up" table of repos, tags, commits ... and but probably want to emphasize "for detailed info on repositories, branches and tags for debugging purposes, see: "buildlogs/relengdirectory.txt (which is currently "buried" several pages down in "releng logs". Another improvement could be so simplify the "(Supported Versions)" links.
These are currently listed next to 10 of the 15 downloads ... but a) all point to the same place ("Target Platforms" of plan) and b) no reason it doesn't equally apply to all 15 downloads, as much as the 10 that have it. That is, Solaris, HP-UX, and AIX are also listed in plan, even though they have no link.
These are currently listed in the SDK section, binary platform section, and swt section -- all point to the same place.
I think at most we only need mention and link to it once, either as a whole seperate link ... perhaps as part of the "Related Links" at top of page (that'd be easiest to implement), or perhaps simply after column heading of 'Platform' (which would be harder to implement).
I've probably another bug for this one ... it annoys me so much ... but instead of having a whole column that says nothing but "http" (and links to download the file named in other column, the file name itself should be the "link" to begin the http download. (I know this is historical left over ... from when we had 'http' choice and 'ftp' choice'. All the information here is no longer relevant with current build process. |