Re: [eclipse.org-planning-council] Next Planning Council call : May2

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

Hi Nick

If you read and
heard my (and other) comments, you know that neither "R" nor
"Tres" nor "SimRel" is really good in my opinion. It
has zero meaning to 80% (just a guess) of our users. so, would be a really
bad choice. Anyway, It would be fine with me as long as we do not use it
when talking to users like in the splash screen, but only for us "internally".

Dani



From:
       Nick
Boldt <nboldt@xxxxxxxxxx>
To:
       Eclipse
Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>,
"gunnar@xxxxxxxxxxxxxxx" <gunnar@xxxxxxxxxxxxxxx>
Date:
       03.05.2018
17:37
Subject:
       Re:
[eclipse.org-planning-council] Next Planning Council call : May2
Sent
by:        eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

Dani,

From another thread from Gunnar re: feedback
from the board:

> It's
my understanding that the requirement for any name is that it *must* comply
with the Foundation's project naming and branding guidelines. 
> The name "Eclipse MM-YYYY"
does not comply. Thus, it simply won't be possible. There must be a qualifier.

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

Thus we can't call it "Eclipse 2018-09"
because we need a qualifier. That qualifier, barring any better
suggestions, was decided yesterday to be simply "SimRel".

Therefore the name is "Eclipse SimRel
2018-09". 

I also suggested on the call (via the
chat feature) that we could call it something like:

* Eclipse S 2018-09, and in marketing
materials this could be "Eclipse
S 2018-09 release" or more colloquially "Eclipse's
2018-09 release"*; or

* Eclipse R 2018-09, since the next logical
letter after the alphabetically named releases (if we skip Q) is R. Then
marketing could be "Eclipse Release 2018-09" to make it clear
what the R stands for. Or "Eclipse r2018-09" if we want the r
to look like a revision prefix. Either way software people know what the
R is for: the next revision or release. 

Either no one saw the chat comments,
or it was decided that a single letter qualifier is worse than "SimRel".
In any case, it's SimRel now.

If the board / community / EMO really
hates this new name, we could always revisit my other idea of calling the
train "Tres". See https://bugs.eclipse.org/bugs/show_bug.cgi?id=532220#c27

The good news is that if we do the sept
release as "SimRel" we would still be able to maintain alphabetic
sequencing if in December 2018 or March 2019 we decide we need a qualifier
that starts with a "T". :D 

Cheers,

Nick

* - because clever punctuation makes
me happy, I guess


On Thu, May 3, 2018 at 11:20 AM, Daniel
Megert <daniel_megert@xxxxxxxxxx>
wrote:
Maybe I did not
have enough coffee, but I can't remember that we decided to use


Eclipse SimRel YYYY-MM 

I thought we just drop everything but the date and let the splash screen
communicated what it is. As mentioned "SimRel" is stupid because
most users have no clue what this means. If at all, we'd have to use the
full name.

Dani



From:        "Mélanie
Bats" <melanie.bats@xxxxxxx>
To:        eclipse.org-planning-council@xxxxxxxxxxx
Date:        03.05.2018
12:01
Subject:        Re:
[eclipse.org-planning-council] Next Planning Council call : May  
     2
Sent by:        eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

Hi,

Le 30/04/2018 à 11:02, Mélanie Bats a écrit :

The minutes from yesterday meetings are online:
https://wiki.eclipse.org/Planning_Council/May_2_2018

Please review and complete my notes on the wiki.

Thanks,
-- 
Mélanie Bats
CTO
+33 7 87 69 42 84
+33 5 34 57 16 29
@melaniebats

*Obeo*
25 Boulevard Victor Hugo - Colomiers - France
http://www.obeo.fr
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.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@xxxxxxxxxxxto request removal.

_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.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@xxxxxxxxxxxto request removal.

--

Nick Boldt

Senior 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://dev.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.