| Summary: | New download page has no version numbers | ||
|---|---|---|---|
| Product: | Community | Reporter: | benson margulies <bimargulies> |
| Component: | Website | Assignee: | phoenix.ui <phoenix.ui-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | gunnar |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
benson margulies
Note sure if you recognized the orange box in the top right saying "eclipse europa is here". "europa" is actually the version of the whole thing. The problem is that the packages are build out of many different plug-ins from various projects. Not sure which version number should be there ... just the Eclipse Platform number? BTW, asking build IDs on bug submission forms is quite common. But yeah, it may not make sense for all Bugzilla products/component combinations. Up until this time around, the only version scheme I've ever seen is the number that went from 3.0 to 3.1 to 3.2 to 3.3. I can see why you'd want to invent a new version naming scheme to tame the situation with all the many components, but I guess I'd have found it a lot less confusing if the transition were explicit on the download page. 'We used to name all eclipse downloads by the platform version number, but now ...' My cavail about the build id was really just lame humor. Since I was complaining that I didn't see a single version number on the web page, I felt some irony in being asked to specify a version number in the bug report. I admit it would be nice to know that all the packages/downloads are based on/for Eclipse 3.3. +1 for "based on Eclipse Platform 3.3" or something along the lines I've "solved" this as part of bug 199636 by adding the word "Europa" to the section header. I went against using 3.3 for consistency between the Eclipse splash screen which sais "Europa", not 3.3. *** This bug has been marked as a duplicate of bug 199636 *** |