Bug 510201 - Naming Oxygen+1 (2018 Eclipse Simultaneous Release)
Summary: Naming Oxygen+1 (2018 Eclipse Simultaneous Release)
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Architecture Council (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: eclipse.org-architecture-council CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-10 11:52 EST by Chris Aniszczyk CLA
Modified: 2018-05-15 15:59 EDT (History)
42 users (show)

See Also:


Attachments
Eclipse pluto branding (23.40 KB, image/png)
2017-01-12 09:43 EST, Matthew Khouzam CLA
matthew.khouzam: iplog-
matthew.khouzam: review-
Details
Eclipse perseids splash (518.08 KB, image/png)
2017-01-12 17:42 EST, Matthias Sohn CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Aniszczyk CLA 2017-01-10 11:52:31 EST
The rules and procedure for naming Neon+1 will be similar to what has happened in the past (see bug 483685 as an example). The name should be alphabetically greater than "O" 

Preference will be given to "P" names, but no strict rule that others would not be considered. Preference given to names that fit the "moon", "heavenly body gods", or "scientists" themes we've had in the past.

This cross-project bugzilla entry will remain open to solicit names, until December 15th to gather suggestions for potential names. The planning council will then meeting and remove any names deemed unsuitable for any reason (as always, the Planning Council has final responsibility for the name).

Following the gathering of the list of names in this bugzilla, a community poll will be used to pick top choice. We may have a series of run-off polls, voting until majority achieved. The poll should be opened by in late December or early January with a week of voting allowed.

The final decision on the name will be made by Feb 15th at the latest.
Comment 1 Dani Megert CLA 2017-01-10 11:55:39 EST
Pluto
Comment 2 Doug Schaefer CLA 2017-01-10 12:49:58 EST
Eclipse 18
Comment 3 Michael Scharf CLA 2017-01-10 12:57:41 EST
Eclipse 2018.6

All those numbers and names are confusing. I really think the release date is the best indicator.
Comment 4 Nick Boldt CLA 2017-01-10 13:33:28 EST
Some planets/moon names (or just names from Greek mythology):

Pluto
Phobos
Phocus
Poseidon
Proteus
Prospero

Scientists/Mathematicians:

Ptolemy
Planck
Pauling
Pascal
Pythagoras
Pavlov
Pasteur
Pauli

And just because it's the name of a volcano in the Azores / tallest point in all of Portugal, and equal to 1 trillionth:

Pico (or Piquinho)

----

To bridge the divide between the "use a codename, like we have for over a decade" camp and the "just use a number / release year" camp, we could be go with BOTH the release date and a bracketed codename, eg.,

* Eclipse 2018.06 (Pico)
* Eclipse 2018.09 (Pico.1)
* Eclipse 2018.12 (Pico.2)
* Eclipse 2019.03 (Pico.3)

Personally, I believe we NEED a name (or both a date and a name), because the pre-release milestones for the Qx release (2019) will be released nearly in parallel with the Px.1, Px.2, and Px.3 (where Px = Oxygen+1) maintenance releases, leading to confusion. 

For example, is "Eclipse 2017.09" the .1 maintenance release of the Eclipse 4.7.1.R-based simrel stream (Oxygen)? Or the M2 milestone for the Eclipse 4.8.0.M2-based stream (Px name TBD)? 

We'll have this confusion of nearly overlapping releases 3 times a year, going forward:

* Oxygen.1 and Px.0.M2 in September 2017 ... both could be called Eclipse 2017.09
* Oxygen.2 and Px.0.M4 in December 2017  ... both could be called Eclipse 2017.12
* Oxygen.3 and Px.0.M6 in March 2018     ... both could be called Eclipse 2018.03

* Px.1 and Qx.0.M2 in September 2018 ... both could be called Eclipse 2018.09
* Px.2 and Qx.0.M4 in December 2018  ... both could be called Eclipse 2018.12
* Px.3 and Qx.0.M6 in March 2019     ... both could be called Eclipse 2019.03
Comment 5 Fred Bricon CLA 2017-01-10 15:04:54 EST
+1 for Pluto, provided we don't get in trouble with Disney lawyers 

> Personally, I believe we NEED a name (or both a date and a name), because
> the pre-release milestones for the Qx release (2019) will be released nearly
> in parallel with the Px.1, Px.2, and Px.3 (where Px = Oxygen+1) maintenance
> releases, leading to confusion. 
> 

Very good point.
Comment 6 George Gastaldi CLA 2017-01-10 15:29:43 EST
+1 to Pluto
Comment 7 Chris Aniszczyk CLA 2017-01-10 15:38:36 EST
Just for clarification, we will solicit names from the community until Jan 20th and than do a community poll (sigh copy paste)
Comment 8 Eike Stepper CLA 2017-01-11 01:18:05 EST
Proton
Photon
Plasma
Proximity
Power
Particle
Pascal
Polar
Parsec
Perihelion
Planet :P
Protuberance
Positron
Ptolemy
Palladium
Pan (Unofficial name for Jupiter XI. Discovered by Nicholson in 1938.)
Panstellar
Parallax
Penrose (Roger)
Perseus
Phobos (Mars moon)
Pion
Pioneer
Planck
Polaris (the North Star)
Poseidon (god or unofficial name for Jupiter VIII)
Potassium
Prime
Pulsar
Pulse
Comment 9 Till Brychcy CLA 2017-01-11 03:06:49 EST
Pegasus
Comment 10 Jeff MAURY CLA 2017-01-11 03:09:56 EST
Pluto
Photon
Polar
Comment 11 Max Bureck CLA 2017-01-11 17:02:54 EST
+1 Pluto
Photon is not bad, too
Comment 12 Werner Keil CLA 2017-01-11 17:09:06 EST
+1 Pluto

Prometheus (Greek mythology and thanks to Ridley Scott also a flying object in Space)
Comment 13 Jesse McConnell CLA 2017-01-11 17:10:49 EST
Psion
Comment 14 Werner Keil CLA 2017-01-11 17:14:12 EST
Platin or 
Platinum another element

-1 for Polar, it would sound a bit too much like PolarSys IMHO.
Comment 15 Nick Boldt CLA 2017-01-11 17:20:57 EST
After Neon and Oxygen, why not keep the chemistry train going?

Plasticity (capacity of a substance to be molded or altered)
Phosphorus (symbol is P, so could be Eclipse P)
Comment 16 Matthias Sohn CLA 2017-01-11 19:23:00 EST
- Pandora (moon of Saturn)
- Phoebe (moon of Saturn)
- Pleiades (brightest open cluster of stars in the sky)
- Polygon
- Phonon (vibrational modes in a crystal lattice)
Comment 17 Mickael Istria CLA 2017-01-12 02:41:12 EST
(In reply to Fred Bricon from comment #5)
> +1 for Pluto, provided we don't get in trouble with Disney lawyers 

Can't wait to see an Eclipse splashscreen featuring Disney's Pluto :D
Comment 18 Kaloyan Raev CLA 2017-01-12 03:11:18 EST
Pi

If we still had the Eclipse 3.x release line, in 2018 we would have had Eclipse 3.14.
Comment 19 Celine Janssens CLA 2017-01-12 03:21:37 EST
I have a preference for those: 

- Prion
- Planck
- Pluto
- Prometheus
Comment 20 Roxanne Joncas CLA 2017-01-12 04:53:45 EST
(In reply to Mickael Istria from comment #17)
> (In reply to Fred Bricon from comment #5)
> > +1 for Pluto, provided we don't get in trouble with Disney lawyers 
> 
> Can't wait to see an Eclipse splashscreen featuring Disney's Pluto :D

If only we could ^^
Comment 21 Arnaud Cuccuru CLA 2017-01-12 05:44:04 EST
Proxima (Centauri)
Comment 22 Tristan Faure CLA 2017-01-12 05:45:14 EST
Agree with some comments
I like the idea to have a name and I'm also ok with the fact that people outside the community is not aware of this name.

So I would prefer to have internal name (hidden or not and the community can use it because it is more fancy) : +1 Pluto 

and the release year : Pluto.2018
Comment 23 Eike Stepper CLA 2017-01-12 06:04:32 EST
Ten years ago Pluto's status was "downgraded" because it was no longer leading its competitors. Ouch :P
Comment 24 Florin Herinean CLA 2017-01-12 06:47:11 EST
As a user of eclipse, developing with multiple versions of eclipse, the most important thing to me is the version.

The year is totally irrelevant.

For names, I prefer either one of

Pascal
Pluto
Comment 25 Marc Khouzam CLA 2017-01-12 07:47:32 EST
(In reply to Florin Herinean from comment #24)
> As a user of eclipse, developing with multiple versions of eclipse, the most
> important thing to me is the version.
> 
> The year is totally irrelevant.

The year would be the version.  You could keep track just like you do now, but also realize how old a particular version was.
Comment 26 Patrick Tasse CLA 2017-01-12 09:18:50 EST
+1 Photon

After the Eclipse comes the light
Comment 27 Matthew Khouzam CLA 2017-01-12 09:42:27 EST
Pluto would make Neil Degrasse Tyson demote the release to a dwarf release. Do we really want that? I do!

I actually prefer Phobos, it has a nice BFG ring to it.

Planck is pretty cool, simple and rolls off the tongue. It is also good to show that eclipse is trying to lean up.

Perseids could be a great timing opportunity as the perseid showers would be starting around the time of the release.

// --- fun stuff below ---

How about some star trek? 
Eclipse: Phasor
Eclipse: Picard

Better than the star wars
Eclipse: Phantom Menace
Comment 28 Matthew Khouzam CLA 2017-01-12 09:43:41 EST
Created attachment 266273 [details]
Eclipse pluto branding

Here is a quick mock up of what eclipse pluto would look like.
Comment 29 Matthias Sohn CLA 2017-01-12 17:42:48 EST
Created attachment 266287 [details]
Eclipse perseids splash

here's how the Eclipse perseids splash screen could look like
Comment 30 Matthew Khouzam CLA 2017-01-12 22:33:50 EST
(In reply to Matthias Sohn from comment #29)
> Created attachment 266287 [details]
> Eclipse perseids splash
> 
> here's how the Eclipse perseids splash screen could look like

That is gorgeous.
Comment 31 Chandrayya CLA 2017-01-13 04:47:41 EST
1. Choose any code name.
2. Don't considered release date/year as version number(as in Ubuntu)
3. Everything needs to be displayed on splash screen like in the format:

<Code Name><saparator><Version Number><saparator><Release date>

<Code Name> = ?|<Selected by community or empty>

<saparator> = :|.|*| or good looking icons like filled square, circle, diamond etc

<Version Number> = Short | Long ex; 4.6.0 or 4.6.0.v20160606-1100 (Platform plugin version>

<Release date> = ? | If not used long version number then,
Released on 2016/06/24 |  Released on 24th June 2016
Comment 32 Jens Reimann CLA 2017-01-13 05:41:39 EST
IMHO a simple name is easier to handle than a technically correct release/version number. You can still add that number to the release as a reference though.

+1 for:
 * Photon
 * Pluto
Comment 33 Kaloyan Raev CLA 2017-01-13 05:43:59 EST
(In reply to Matthias Sohn from comment #29)
> Created attachment 266287 [details]
> Eclipse perseids splash
> 
> here's how the Eclipse perseids splash screen could look like

Tagline: "Make a wish!"
Comment 34 Frederic Gurr CLA 2017-01-13 06:38:16 EST
(In reply to Nick Boldt from comment #4)
> To bridge the divide between the "use a codename, like we have for over a
> decade" camp and the "just use a number / release year" camp, we could be go
> with BOTH the release date and a bracketed codename, eg.,
> 
> * Eclipse 2018.06 (Pico)
> * Eclipse 2018.09 (Pico.1)
> * Eclipse 2018.12 (Pico.2)
> * Eclipse 2019.03 (Pico.3)
> 
> Personally, I believe we NEED a name (or both a date and a name), because
> the pre-release milestones for the Qx release (2019) will be released nearly
> in parallel with the Px.1, Px.2, and Px.3 (where Px = Oxygen+1) maintenance
> releases, leading to confusion. 
> 
> For example, is "Eclipse 2017.09" the .1 maintenance release of the Eclipse
> 4.7.1.R-based simrel stream (Oxygen)? Or the M2 milestone for the Eclipse
> 4.8.0.M2-based stream (Px name TBD)? 
> 
> We'll have this confusion of nearly overlapping releases 3 times a year,
> going forward:
> 
> * Oxygen.1 and Px.0.M2 in September 2017 ... both could be called Eclipse
> 2017.09
> * Oxygen.2 and Px.0.M4 in December 2017  ... both could be called Eclipse
> 2017.12
> * Oxygen.3 and Px.0.M6 in March 2018     ... both could be called Eclipse
> 2018.03
> 
> * Px.1 and Qx.0.M2 in September 2018 ... both could be called Eclipse 2018.09
> * Px.2 and Qx.0.M4 in December 2018  ... both could be called Eclipse 2018.12
> * Px.3 and Qx.0.M6 in March 2019     ... both could be called Eclipse 2019.03

+1 for Photon
+1 for release year + bracketed codename

To prevent confusion with overlapping, I'd recommend to adapt a proven numbering system (Ubuntu). For example (I chose Photon as codename here):

* Eclipse 18   (Photon)
* Eclipse 18.1 (Photon.1)
* Eclipse 18.2 (Photon.2)
* Eclipse 18.3 (Photon.3)

So the Oxygen service releases could be called

* Eclipse 17.1 (Oxygen.1)
* Eclipse 17.2 (Oxygen.2)
* Eclipse 17.3 (Oxygen.3)

Why not 2018.06, 2018.06.1, etc? The 20 prefix will be redundant (for the next 82 years at least ;) ) and since we only have one mayor release per year (not two like Ubuntu) the month doesn't matter either. IMHO, a user does not care about the month in which the mayor or service release was published, she/he just wants a consistent and easy to grasp numbering system.

Just for illustrative purposes, compare the following two conversations:
A: "Hey, I have a problem with Eclipse?"
B: "OK, which version are you using?"
A: "Mars"
B: "Oh, which version was that? Was that last year's release?"

C: "Hey, I have a problem with Eclipse?"
D: "OK, which version are you using?"
C: "15"
D: "Ah, that's almost two years old. Did you try updating?"
Comment 35 Michael Scharf CLA 2017-01-13 08:13:35 EST
(In reply to Frederic Gurr from comment #34)
> * Eclipse 18   (Photon)
> * Eclipse 18.1 (Photon.1)
> * Eclipse 18.2 (Photon.2)
> * Eclipse 18.3 (Photon.3)

I really like this scheme!
Comment 36 Thorsten Heit CLA 2017-01-13 09:15:03 EST
+1 for Eclipse Pluto (Pluto the (dwarf) planet, not the dog from Disney ;-))

Or: Eclipse Prometheus (after one of Saturn's moons)
Comment 38 Greg Watson CLA 2017-01-13 11:34:07 EST
-1 for Ptolemy as it's already a well established project: http://ptolemy.eecs.berkeley.edu
Comment 39 Vincenzo Caselli CLA 2017-01-16 05:29:10 EST
(In reply to Michael Scharf from comment #35)
> (In reply to Frederic Gurr from comment #34)
> > * Eclipse 18   (Photon)
> > * Eclipse 18.1 (Photon.1)
> > * Eclipse 18.2 (Photon.2)
> > * Eclipse 18.3 (Photon.3)
> 
> I really like this scheme!

I like it too! 
As for the name, +1 for: 

- Photon
- Plasma
- Parsec
- Prime
- Pulsar
- Pulse
Comment 40 Dobromir Zahariev CLA 2017-01-16 13:35:14 EST
+1 Photon
Comment 41 Mateusz Matela CLA 2017-01-27 07:59:56 EST
Did I miss the voting?

BTW, +1 Phobos :)
Comment 42 Sarika Sinha CLA 2017-01-30 04:06:12 EST
+1 for Pulse
Comment 43 Noopur Gupta CLA 2017-01-30 04:16:55 EST
+1 for Pulsar.
And Oxygen+1+1 could be Quasar.

Also, +1 for:
Plasma
Pulse
Comment 44 Celine Janssens CLA 2017-01-30 05:19:29 EST
+1 Pandora
Comment 45 Chris Aniszczyk CLA 2017-02-01 09:53:53 EST
Hey all, sorry for the delay but finally got around to vetting the initial list of names and got it down to 20:
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_857d2f9744a2ea31&akey=fc8b3994ee373613

I eliminated names based on any obvious trademark issues or conflicts with existing Eclipse project names (ecosystem wide).

Please take the time to vote. I will announce the poll publicly tomorrow.

The poll ends Feb 8th 12:00pm ET.
Comment 46 Chris Aniszczyk CLA 2017-02-01 09:54:09 EST
Hey all, sorry for the delay but finally got around to vetting the initial list of names and got it down to 20:
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_857d2f9744a2ea31&akey=fc8b3994ee373613

I eliminated names based on any obvious trademark issues or conflicts with existing Eclipse project names (ecosystem wide).

Please take the time to vote.

The poll ends Feb 8th 12:00pm ET.
Comment 47 Leo Ufimtsev CLA 2017-02-01 10:14:48 EST
Imho "Pi" might not be a good choice because it might make people think that that version is specifically only for the raspberry pi architecture.
Comment 48 Markus Keller CLA 2017-02-01 12:26:01 EST
(In reply to Chris Aniszczyk from comment #46)
> http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_857d2f9744a2ea31&akey=fc8b3994ee373613

That link doesn't work. It opens a page that wrongly says:

Already voted
A vote has already been cast using your voter key.
Comment 49 Chris Aniszczyk CLA 2017-02-01 12:27:46 EST
(In reply to Markus Keller from comment #48)
> (In reply to Chris Aniszczyk from comment #46)
> > http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_857d2f9744a2ea31&akey=fc8b3994ee373613
> 
> That link doesn't work. It opens a page that wrongly says:
> 
> Already voted
> A vote has already been cast using your voter key.

Markus, it simply does vote per IP so I'm guessing the way networking is setup at work is your issue. It's not the most ideal setup but maybe you can vote when you get home or via your phone.
Comment 50 Matthew Khouzam CLA 2017-02-01 13:02:45 EST
This set up means one vote per company depending on their network setup. :( 

Patrick Tasse and I cannot vote because of this set up.
Comment 51 Chris Aniszczyk CLA 2017-02-01 13:04:53 EST
(In reply to Matthew Khouzam from comment #50)
> This set up means one vote per company depending on their network setup. :( 
> 
> Patrick Tasse and I cannot vote because of this set up.

It's not ideal but hopefully voting from home works. I hesitate of going back to our old way of voting (vs the current Condorcet style setup).
Comment 52 Chris Aniszczyk CLA 2017-02-08 13:36:57 EST
Voting is over, top 3 results are:

1. Pluto  (Condorcet winner: wins contests with all other choices)
2. Photon  loses to Pluto by 137–95
3. Phobos  loses to Pluto by 147–68, loses to Photon by 129–80

Vetting of the names will happen here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=511933

Thanks everyone who voted!
Comment 53 Chris Aniszczyk CLA 2017-02-27 16:44:26 EST
via https://bugs.eclipse.org/bugs/show_bug.cgi?id=511933#c4

"I am happy to announce that the name "Eclipse Photon" has been approved for use as the 2018 simultaneous release name."

Thanks for everyone who participated in the process!
Comment 54 Werner Keil CLA 2018-03-09 15:58:03 EST
(In reply to Chris Aniszczyk from comment #53)
> via https://bugs.eclipse.org/bugs/show_bug.cgi?id=511933#c4
> 
> "I am happy to announce that the name "Eclipse Photon" has been approved for
> use as the 2018 simultaneous release name."
> 
> Thanks for everyone who participated in the process!

Great, what about the 2019 release, is it no longer going to have a name like that?
Comment 55 Nick Boldt CLA 2018-05-15 12:59:27 EDT
(In reply to Werner Keil from comment #54)
> Great, what about the 2019 release, is it no longer going to have a name
> like that?

There's been some lengthy discussion about the future releases' names.

https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg03039.html

https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg03033.html

There has not been consensus yet, however.
Comment 56 Matthew Khouzam CLA 2018-05-15 15:32:07 EDT
I'm going to go ahead and suggest Eclipse Quasar, Eclipse Quark, Eclipse Quantum and Eqlipse right away.

To get them out of the way, I really like Quadrature: 
* it sounds serious
* it has to do with the moon and sun's position, it plays well with eclipse
* it refers to something cyclical like a release
* the splash screen will look nice with lots of right angles
Comment 57 Leo Ufimtsev CLA 2018-05-15 15:44:05 EDT
(In reply to Matthew Khouzam from comment #56)
> I'm going to go ahead and suggest Eclipse Quasar, Eclipse Quark, Eclipse
> Quantum and Eqlipse right away.

I like Quantum. Sounds familiar and cool.
Comment 58 Nathan Ridge CLA 2018-05-15 15:54:03 EDT
(In reply to Leo Ufimtsev from comment #57)
> (In reply to Matthew Khouzam from comment #56)
> > I'm going to go ahead and suggest Eclipse Quasar, Eclipse Quark, Eclipse
> > Quantum and Eqlipse right away.
> 
> I like Quantum. Sounds familiar and cool.

Firefox had a release named Quantum which was well-received and won a lot of people back from Chrome.

Perhaps we can start a trend :)
Comment 59 Mickael Istria CLA 2018-05-15 15:59:26 EDT
(In reply to Nick Boldt from comment #55)
> There's been some lengthy discussion about the future releases' names.
> https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg03039.
> html
> https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg03033.
> html
> There has not been consensus yet, however.

Last comment from Melanie on bug 532220 seems to make it pretty clear that while there is still room for discussion about minor details, there won't be release specific names any more.
So unless I'm mistaken, not need to brainstorm about a Q* something name, it won't be used.