threads / discuss / 14656

[EGIT] Supported Eclipse version

Subject: [EGIT] Supported Eclipse version

## tl;dr

5 messages between Jul 24, 2008 and Jul 25, 2008.

replies: 4people: 4as markdown or json

Marek Zawirski· Jul 24, 2008, 13:57 UTC · lore

This topic arose after 3.4 release. Are we dropping support for 3.2.x release or not?

I've recently reported some bug at eclipse.org bugzilla regarding broken FileDialog for 3.3.x and it was closed, marked as resolved in 3.4 with comment that 3.3.x stream is finished. Actually, this bug is not critical, just annoying.

It just seems that eclipse.org is trying to force users to update their Eclipse soon after next stable release. 3.3 also added some interesting APIs, Robin mentioned it one day. I'm currently just touching TableViewer API and it also have some nice new features being available since 3.3.

Do we still have to be compatible with 3.2 release? It's about 2 years old, with last synchronized release/build February 2007. On the other hand, some commercial tools are still based upon 3.2 release.

Maybe some users (or developers) from mailing list can tell us about their opinion?

Marek Zawirski

Jean-François Veillette· Jul 24, 2008, 14:07 UTC · re: Marek Zawirski · lore

Re: [EGIT] Supported Eclipse version

> Maybe some users (or developers) from mailing list can tell us  
> about their opinion?

I think keeping comptability for one version behind the 'current' (still compatible 3.3 while 3.4 is the current) is a reasonable goal. 3.2 is relatively far behind, tools vendor had time to get up to date by now. If a user is using a third party version of eclipse based on 3.2, then I guess he should not expect egit to work with it (he should just pray and hope for the best).

For myself, I use 3.3.x, I have not yet moved to 3.4 since my main plugin (WOLips) is not ready yet for 3.4.

- jfv

Marek Zawirski· Jul 25, 2008, 14:12 UTC · re: Jean-François Veillette · lore

Re: [EGIT] Supported Eclipse version

Jean-François Veillette wrote:

Show 15 quoted lines

>> Maybe some users (or developers) from mailing list can tell us about 
>> their opinion?
>
> I think keeping comptability for one version behind the 'current' 
> (still compatible 3.3 while 3.4 is the current) is a reasonable goal.
> 3.2 is relatively far behind, tools vendor had time to get up to date 
> by now.
> If a user is using a third party version of eclipse based on 3.2, then 
> I guess he should not expect egit to work with it (he should just pray 
> and hope for the best).
>
> For myself, I use 3.3.x, I have not yet moved to 3.4 since my main 
> plugin (WOLips) is not ready yet for 3.4.
>
> - jfv

I would also vote for this change. Especially if there are not many users screaming that they need egit in Eclipse 3.2.

BTW, I'm using 3.4 version for 2 days and it looks really nice. What's important, it seems to not be that buggy as early 3.3 releases were.

Robin, Shawn, would you accept next patches using 3.3 API?

Marek

Shawn O. Pearce· Jul 25, 2008, 16:16 UTC · re: Marek Zawirski · lore

Re: [EGIT] Supported Eclipse version

Marek Zawirski <marek.zawirski@gmail.com> wrote:

Show 10 quoted lines

> Jean-François Veillette wrote:
>>> Maybe some users (or developers) from mailing list can tell us about  
>>> their opinion?
>>
>> I think keeping comptability for one version behind the 'current'  
>> (still compatible 3.3 while 3.4 is the current) is a reasonable goal.
>> 3.2 is relatively far behind, tools vendor had time to get up to date  
>> by now.
>
> Robin, Shawn, would you accept next patches using 3.3 API?

Yes, we should be dropping support for 3.2 now and supporting only 3.3 and 3.4 going forward. 3.2 is ancient and anyone who is serious aboug using Git with Eclipse really should be on a more current version of the tools.

Same argument that Junio gave about not supporting Debian users who are still installing git 1.4.4.4 and hope it works; we suggest they install the 1.5.x based backport as soon as possible.

Commercial Eclipse distributions that are still based upon 3.2 should be upgrading themselves to 3.3 real soon, and if not, their users should be forching them to do it.

-- 
Shawn.

Robin Rosenberg· Jul 25, 2008, 19:35 UTC · re: Shawn O. Pearce · lore

Re: [EGIT] Supported Eclipse version

fredagen den 25 juli 2008 18.16.52 skrev Shawn O. Pearce:

Show 16 quoted lines

> Marek Zawirski <marek.zawirski@gmail.com> wrote:
> > Jean-François Veillette wrote:
> >>> Maybe some users (or developers) from mailing list can tell us about  
> >>> their opinion?
> >>
> >> I think keeping comptability for one version behind the 'current'  
> >> (still compatible 3.3 while 3.4 is the current) is a reasonable goal.
> >> 3.2 is relatively far behind, tools vendor had time to get up to date  
> >> by now.
> >
> > Robin, Shawn, would you accept next patches using 3.3 API?
> 
> Yes, we should be dropping support for 3.2 now and supporting only
> 3.3 and 3.4 going forward.  3.2 is ancient and anyone who is serious
> aboug using Git with Eclipse really should be on a more current
> version of the tools.

We already dropped 3.2 compatibility with the push/fetch support. That was an accident, of course.

Support for 3.3 could also end ahead of schedule if we absolutely need some feature that is only available in 3.4. We'll discuss that then, when/if it happens. The plan is to support 3.3 until 3.5 is out (or even longer if that requires no effort).

So much for intent. We reserve the right to change our minds or make mistakes without notice.

-- robin