[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse.org-planning-council] SimRel Naming
- From: Ed Merks <ed.merks@xxxxxxxxx>
- Date: Fri, 4 May 2018 17:39:37 +0200
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
On 04.05.2018 16:58, Gunnar Wagenknecht wrote:
Perhaps what's left then is next to nothing.Â Just some "docs" whatever
those might be.ÂÂ And perhaps the "public" doesn't care about the train
nor what we call it.Â They'll only care that the Eclipse IDE for Java
Developers has a new 2018-09 version that supports Java 11.ÂÂ Or that
the Eclipse IDE for Java EE Developers has a 2018-09 version that
supports all the cool stuff in the Eclipse Jarkata 2018-09 stuff; okay,
I'm dreaming a little. :-PÂ But I expect that in the end the public will
care about updates to their favorite tool, technology or framework, and
about what's new and noteworthy, and won't give a hoot about what we
call out train.
On May 4, 2018, at 16:29, Ed Merks <ed.merks@xxxxxxxxx> wrote:
Given that I excluded URL and Splash above and EPP before. What is left? Mostly docs and public naming of the release train.
And "name:" here is used what context?
splash screen: "Photon" -> number ==> ok
url: "Photon" -> number ==> ok
name: "Photon" -> number ==> not sufficient (based on branding guidelines)
So what do we do with the name?
Indeed, where do we use this name?
As long as we generally useÂ the term/name internally, SimRel seems
fine.Â When we need a term/name for external purposes, it's probably
better to avoid that need and to describe what it is rather than assign
a name/term to it.
But isn't that what people don't like and want to replace? Or is SimRel good?
The Planning Council decided to use SimRel for the time being.
Propsals so far:
- Desktop IDE
What is your vote for the name then?
eclipse.org-planning-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.