[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] Dropping the release names (Neon, Oxygen) from user downloads

Sounds good.
BTW, IntelliJ is also moving to naming releases on a year basis: https://blog.jetbrains.com/blog/2016/03/09/jetbrains-toolbox-release-and-versioning-changes/

However, to me an even more important aspect is that Eclipse doesn't automatically update across major releases. This will be even more confusing if Eclipse adopts a year-based naming scheme, because the user will either expect continuous updates forever, or alternatively that a new download/manual-installation is required for the first release of a new year.

Consider Doug's example, a major release is done in 2016, then a follow-up minor release on 2017. If the minor release is called 2016.3 even though its 2017, it's confusing. But if it's called 2017.1, but Eclipse only updates automatically to 2017.1, but not to 2017.2 (because say, that would be a new major release), it's even more confusing...


On 28 April 2016 at 14:33, Tracy Miranda <tracy@xxxxxxxxxxxxxxxx> wrote:
Hi all,Â

In thinking about the Eclipse IDE more as a product, I want to toss up the suggestion of dropping the release names i.e Neon, Oxygen from anything user facing i.e. download site, etc.Â

I wrote up these thoughts in a postÂhttps://kichwacoders.com/2016/04/28/why-its-time-to-kill-the-eclipse-release-namesneon-oxygen-etc/

The summary is that they unnecessarily add confusion for anyone not intimately familiar with Eclipse. I suggest replacing the releases simply with the year they go out. Perhaps with some convention for intermediate releases.

Thoughts?

Regards,
TracyÂ

_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev



--
Bruno Medeiros
https://twitter.com/brunodomedeiros