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

Bug 326919

Summary:	Use Version Numbers instead of Cryptic codenames for downloadable files
Product:	[Technology] EPP	Reporter:	Florian R. <rosenauer>
Component:	package content	Assignee:	Project Inbox <epp.packager-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert, denis.roy, john.arthorne, mknauer, thatnitind, wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Florian R.

2010-10-04 09:51:40 EDT

Build Identifier: 

Please name the files e.g. eclipse-3.6-jee-helios-SR1-win32-x86_64.zip instead of eclipse-jee-helios-SR1-win32-x86_64.zip

Maybe a developer or website administrator has memorized the code name to version number table, but not a normal Eclipse user like myself.

I am annoyed of needing Google every time I see a Europe/Galileo/ganymede File and want to know which is the most recent one or a need a specific version (unfortunatelly our developers tend NOT to add the version number to the downloaded file).

Reproducible: Always

Comment 1 Denis Roy

2010-10-04 10:34:52 EDT

Moving to the packaging project for consideration, since they determine their naming schemes.

Comment 2 John Arthorne

2010-10-04 11:00:44 EDT

I don't know if there is a meaningful version number to give here... for example JEE Helios package contains Platform 3.6, Web Tools 3.2, and likely other features with other versions.

FWIW, here is the mapping of names to release dates:

http://wiki.eclipse.org/Simultaneous_Release

I suppose adding the release date (YYYYMMDD) in the file name might help.

Comment 3 Florian R.

2010-10-05 04:03:50 EDT

Maybe it does not make sense, but (for my feeling) everyone is using a kind of global Platform relase version. Adding a release date would not solve this.

e.g. http://pydev.org/download.html refers 3.2/3.3 and 3.4/3.5 for different installation instructions.

also http://www.phpeclipse.com/wiki/Installation

e.g. http://translate.google.at/translate?hl=en&sl=de&u=http://www.heise.de/developer/artikel/Eclipse-4-die-naechste-Generation-der-freien-IDE-962171.html&ei=Z9eqTPnLNcWUOoa11IkH&sa=X&oi=translate&ct=result&resnum=1&ved=0CBQQ7gEwAA&prev=/search%3Fq%3Dsite:heise.de%2Beclipse%2B4%26hl%3Den%26rlz%3D1G1ACALCDEAT322%26prmd%3Div refers Eclipse 4.0 and not Indigo as next big Release

http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA at least combines both Version and Code Name.

The Classic eclipse-SDK-3.6-win32-x86_64.zip still contains that Version Number.

Comment 4 Markus Knauer

2011-05-20 12:21:08 EDT

In case of the Classic package it makes sense because this *is* of version 3.x or 4.x... and if heise.de refers to Eclipse 4.0 they mean the 4.0 release of the Eclipse (Platform) *project*, but that is different from the EPP packages that are based on the input of many, many projects at eclipse.org that are release as part of the yearly Simultaneous Release Train.

The only common denominator for EPP is the Simultaneous Release Train (and no one is interested in the 'internal' EPP version number which would be 1.3 for Helios, 1.4 for Indigo, ...)

You can find a good overview here: http://wiki.eclipse.org/Simultaneous_Release

I am closing this bug as WONTFIX and hope that my explanations help.