Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Subversive » Standardize Feedback after Migration to Eclipse Project
Standardize Feedback after Migration to Eclipse Project [message #10966] Sun, 25 November 2007 15:13 Go to next message
Werner Keil is currently offline Werner Keil
Messages: 1083
Registered: July 2009
Senior Member
Hi,

I just had a first look at your new Eclipse project release.

While the need to install simultaneously from 2 separate Update Sites
(else the dependencies cannot be found and it won't install ;-) is a
little strange and may be a bit better documented or solved in future,
the project makes a good impression otherwise.

Especially other dependencies and connectors are far better solved than
in previous (1.x) releases still developed under the Polarion umbrella.
Most notable platform-specific issues like SVNKit which on non-Windows
environments such as Mac now work properly and are considerd 'Default'.

If you manage to support Mylyn not only when committing sources, but to
replace your proprietary 'Report a Bug' and 'Suggestion' menus only
renamed from 'Polarion' to 'Subversive', this would be great.
After all, Mylyn comes with a default Entry for that in the Help Menu in
the most recent Eclipse versions (3.3, probably in 3.2 too with newer
Mylyn releases?)

Not sure, where the 'Update Projects and Settings' item should otherwise
go, although I would see that under 'Software Updates' if this menu is
open to 3rd party vendors?

Please also note, the Eclipse Babel project is there to support you with
Localization of both the Eclipse Platform as such and other Eclipse
Projects like Subversive.

Feel free to contact us if you have any questions, ideally dropping a
message here in the Newsgroups, too.

Werner
Re: Standardize Feedback after Migration to Eclipse Project [message #10979 is a reply to message #10966] Tue, 27 November 2007 13:04 Go to previous messageGo to next message
Eclipse User
Originally posted by: alexander.gurov.polarion.org

Dear Werner,

Thank you for sharing your opinion.

The installation process is more complex than earlier because we cannot
transfer clients to Eclipse.org due to licensing policies (Subversion
clients contain LGPL-licensed code which is not compatible with the EPL
license). So, two update sites are required.

Unfortunately both clients - SVN Kit and JavaHL – contain different bugs
and we can’t prefer one of them. But another one moment – we do not
provide native libraries for all platforms - makes our choice clear: we
selected SVN Kit as default client in order to avoid thousands of problem
reports about absent native libraries. In any case user is always able to
switch client library in the plug-in preferences.

Also we have plans to integrate our bug report with the Mylyn (or directly
use the Mylyn features instead of both: tips and bugs) in one of future
releases. At the same time we think “Migrate Projects and Settings” action
is placed correctly because it is only applicable for the Subversive
project in case of migration from the Polarion Subversive stream to
Eclipse Subversive stream.

And the last thing is the localization/globalization itself. First of all
thank you very much for your proposal. It is very interesting for us. At
this moment we have localization fragments for Core and UI modules which
contain French and Japanese localization files. Unfortunately we cannot
check it correctness or improve these translations because we don’t have
native speakers in our team. So, I’m right that the Babel project tools
could help us in this task?
Re: Standardize Feedback after Migration to Eclipse Project [message #11059 is a reply to message #10979] Sun, 02 December 2007 13:53 Go to previous message
Werner Keil is currently offline Werner Keil
Messages: 1083
Registered: July 2009
Senior Member
Alexander Gurov wrote:
> Dear Werner,
> Thank you for sharing your opinion.
>
> The installation process is more complex than earlier because we cannot
> transfer clients to Eclipse.org due to licensing policies (Subversion
> clients contain LGPL-licensed code which is not compatible with the EPL
> license). So, two update sites are required.
>
> Unfortunately both clients - SVN Kit and JavaHL � contain different bugs
> and we can�t prefer one of them. But another one moment � we do not
> provide native libraries for all platforms - makes our choice clear: we
> selected SVN Kit as default client in order to avoid thousands of
> problem reports about absent native libraries. In any case user is
> always able to switch client library in the plug-in preferences.
>
> Also we have plans to integrate our bug report with the Mylyn (or
> directly use the Mylyn features instead of both: tips and bugs) in one
> of future releases. At the same time we think �Migrate Projects and
> Settings� action is placed correctly because it is only applicable for
> the Subversive project in case of migration from the Polarion Subversive
> stream to Eclipse Subversive stream.
>
> And the last thing is the localization/globalization itself. First of
> all thank you very much for your proposal. It is very interesting for
> us. At this moment we have localization fragments for Core and UI
> modules which contain French and Japanese localization files.
> Unfortunately we cannot check it correctness or improve these
> translations because we don�t have native speakers in our team. So, I�m
> right that the Babel project tools could help us in this task?
>
>

At least for French, please note, that one initial contributor of the
Babel project is French native speaker from Canada ;-)

Hope that helps?

Werner
Previous Topic:Folder structure in workspace differs from structure in SVN
Next Topic:Strange bundles
Goto Forum:
  


Current Time: Sat Oct 25 06:24:18 GMT 2014

Powered by FUDForum. Page generated in 0.13873 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software