Martin: most important thing to understand about technical versions is that it's always only about the deltas

Sven: Add a common place for putting in the marketing version number (release level)

People get stuff from multiple places and want to know whether they are on the latest

Users only care about marketing number (in the about dialog) and never care about technical numbers

Martin: Make technical numbers less prominent in the about dialog; use the "Build ID" for the marketing number - advantage of build ID (in about.ini) is that it can be changed by a simple re-build without changing any code, and it is prominent in the about dialog

DougS: This is a good idea

Never mix marketing version(s) with technical version(s)

Sven: What about a new Manifest Entry (e.g. "Code Name") in the Bundles

We have to educate people how to put the marketing version number in, and Manifest Editor is more logical than the build ID in about.ini

Ed: changing code just for changing the version is painful

Would we allow bumping the major at the release level even without API breakage?

E.g. AspectJ: Adding new language features is a major new functionality even if API is not changed

Agree that marketing number (release version) is at the project's discretion

Chris: How to talk to people about releases

Talk about train names: e.g. "Release n.n for Eclipse Ganymede"

What to do about multiple releases in one train cycle?

What to do with multiple Platform Streams in 1 year? -- McQ: Platform will make a decision which Stream (3.6 or 4.0 will show up in the train) -- so the train is an interesting distinguisher! - don't solve tomorrow's problems today

Could be multiple train names e.g. "AJDT version n.n for Eclipse Ganymede and Helios"

Most people know the platform version numbers better than the train code names

McQ: Picking up e4 or not will likely be a very organic process...

AI Martin create bugzilla bug for continuing the discussion

Maven

Ed: Maven stuff for EMF, Maven Repositories for the Platform etc?

Bernd: Big discussion at SAP...

Should we have an official Maven Repo at Eclipse?

Just a structured file system (at S3 for instance)

Just talk to the Maven projects - AI Martin create a bug for the discussion