[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-planning-council] Next Planning Council call : May2

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@eclipse.org
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@eclipse.org
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.




_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@eclipse.org
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.



--

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com



âThe Only Thing That Is Constant Is Changeâ -ÂHeraclitus