+1 for the “New Classic”
I’ve tested on win32 and linux32, and while I found some
limitations in the branding / product customization [1] they do not seem to be blockers and I’ve got community input requesting the “New Classic” for M6.
I do request getting the
package description updated on the website [2], which it seems Markus has pushed already.
One question: When my improved branding gets pushed to master shortly after M6, and published to the EPP p2 repo, can end users “check for updates” to obtain
the improved branding ?
I’ve tested the improved branding out of the workspace and it looks good.
[1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=397896#c43
[2]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=397896#c46
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: epp-dev-bounces@xxxxxxxxxxx [mailto:epp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Markus Knauer
Sent: Thursday, March 21, 2013 5:22 PM
To: EPP Developer Mailing List
Subject: [epp-dev] Kepler M6 EPP build
Hi all,
I'd like to get your votes for the following Kepler M6 build:
http://build.eclipse.org/technology/epp/epp_build/kepler/download/20130320-2356/
p2 repositories being used:
http://build.eclipse.org/technology/epp/epp_build/kepler/download/20130320-2356/repository/ and
http://download.eclipse.org/releases/staging/
Thanks and I hope to see many of you at EclipseCon,
Markus