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

I think we mean fiscal years where the year end is in June :).

But really, maybe that's why using the last two digits and calling it a version number makes sense. And given Eclipse started around 2000, it wouldn't be far from the truth.

So Neon would be version 16, Oxygen version 17. And then the .1, .2 for the minor releases.

Hmm, that's my favourite so far.

On Fri, Apr 29, 2016 at 1:55 PM, Nick Boldt <nickboldt@xxxxxxxxx> wrote:
When you say "based on the year", how would that work?

Would it be like defining a school year as it spans two calendar years?

Neon.0, Neon.1, Neon.2, Neon.3,
Oxygen.0, Oxygen.1, Oxygen.2, Oxygen.3 ==>
16-17.0, 16-17.1, 16-17.2, 16-17.3,
17-18.0, 17-18.1, 17-18.2, 17-18.3

Or do you mean we'd drop the notion of the update release number (0,
1, 2, 3) and just use yyyy-mm, like Ubuntu does?

Neon.0, Neon.1, Neon.2, Neon.3,
Oxygen.0, Oxygen.1, Oxygen.2, Oxygen.3 ==>
2016-06, 2016-09, 2016-12, 2017-03,
2017-06, 2017-09, 2017-12, 2017-03


On Fri, Apr 29, 2016 at 10:21 AM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
> For those not on the ide-dev list, there is a discussion over the desire to
> change to numerical release names based on the year. We've talked about
> that, but I'm not sure where we left it.
>
> Doug.
>
> ---------- Forwarded message ----------
> From: Doug Schaefer <cdtdoug@xxxxxxxxx>
> Date: Fri, Apr 29, 2016 at 10:20 AM
> Subject: Re: [ide-dev] Dropping the release names (Neon, Oxygen) from user
> downloads
> To: Discussions about the IDE <ide-dev@xxxxxxxxxxx>
>
>
> The June release has to be significantly named. It is the only release per
> year that allows major version changes to plug-ins. We need to make that
> clear to the community. As such, we can't use the month.
>
> BTW, I'll forward this discussion to the planning council mailing list so
> that they are brought up to speed on our thoughts. I'm not sure they're all
> here.
>
> On Fri, Apr 29, 2016 at 7:45 AM, Carsten Reckord <reckord@xxxxxxxx> wrote:
>>
>> On 29.04.2016 10:44, Gunnar Wagenknecht wrote:
>>>
>>> Here is an experiment - any Chrome users out there? Who can tell me the
>>> last time they looked at the version number of their browser to see if their
>>> browser is old?
>>
>>
>> Actually just a few days ago, but that was coincidental.
>>
>> Chrome and Eclipse versions are pretty much apples and oranges - at least
>> as far as end users are concerned. Chrome has a very strong and smooth
>> update story that does a really good job of making the version irrelevant to
>> me. Eclipse doesn't.
>>
>> If we should ever get to the point where automatic updates can just be
>> applied seamlessly in the background, by all means, let's throw away all
>> user-facing code names and version numbers completely. I'd party hard on
>> that day...
>
>
> Yes, that's where we must head. We have the technology, we just need the
> discipline.
>
>>
>>
>> _______________________________________________
>> 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
>
>
>
>
> _______________________________________________
> 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.



--
Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc.
http://nick.divbyzero.com
_______________________________________________
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.