| Re: [eclipse.org-planning-council] Release Train Name: Eclipse IDE |
Nick,
It's the Eclipse IDE release train. Please don't vote based on a sidetracked discussion on "Classic". This is a made up term used as an example. The Foundation may just use some other term.
FWIW, I like it. It's descriptive and clear to everyone. It's also consistent. Mind you - we already call every single on of our package downloads "Eclipse IDE for <whatever>".
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
> On Oct 29, 2018, at 20:53, Nick Boldt <nboldt@xxxxxxxxxx> wrote:
>
> So it's now the "Eclipse Classic IDE release train 2018-12"?
>
> So much for the brevity of "Eclipse Simrel 2018-12".
>
> -1, since we'll have to deal with "what do you mean by 'Classic'?" questions, and because Coke Classic was introduced to recover from a terrible marketing snafu. Do we REALLY want to remind people of New Coke? Are we implying that failing to name the train something with a Q after Photon was an equally bad marketing decision, but we're not actually introducing a better name, just pragmatically differentiating from the other trains which don't release quarterly?
>
> This feels about as creative as calling the web server httpd to differentiate it from the Apache Foundation.
>
> TL;DR, I think we can do better.
>
> Nick
>
>
> On Mon, Oct 29, 2018 at 11:37 AM Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
> Ed, Alex and I had a meeting with the Eclipse Foundation folks at Eclipse Con Europe. We came to an agreement that our release train can use "Eclipse IDE". We can use this in splash screens, landing pages and everywhere where the scope is clear. The Eclipse Foundation can use another name where the scope is not clear, e.g. downloads page, main page, marketing, etc. Most likely they will use "Eclipse Classic IDE", but that is not yet nailed in stone.
>
> In our Planning Council face-to-face meeting at EclipseCon Europe everyone approved that,
>
> Please vote on our release train name until November 5. We assume silent consensus.
>
> Dani
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
> 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.
>
>
> --
> Nick Boldt
> Principal Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>
> TRIED. TESTED. TRUSTED.
> @ @redhatnews Red Hat
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
> 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.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council
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.
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com