Sorry I have been out of the office on vacation so I am coming into
this in the middle.
The reason we do not have support for Indigo or Helios is that users
typically upgrade very quickly to new releases of Eclipse.
Therefore, it was felt support for really old releases is not
needed. Chris, I know we have a report that shows usage by eclipse
version. Can you publish the results on this list?
Konstantin, if you have stats indicating there is a significant
Indigo and/or Helios community then please feel free to post your
stats too.
Thanks
Ian
On 06/05/2015 1:37 PM, Christopher
Guindon wrote:
Hi Konstantin,
Please see below for my comments:
On 2015-05-01 12:12 PM, Konstantin
Komissarchik wrote:
Thanks
for the first set of answers. More questions/comments:
1.
I see that versions prior to Juno are only supported as a
single bucket (previous to juno - <= 4.1). Is there a
technical reason that this couldn’t be implemented? We
have Indigo and Helios variants of our solutions. It
sounds like I’d either have to keep the “for Indigo” and
“for Helios” as separate solutions or drop support for
those platforms through Marketplace.
You are correct, you currently need a separate listing for each
solution version compatible with releases prior to Juno because
the MP REST API will only return 1 possible solution version that
matches the environment of the user.
I created a bug to include Helios and indigo in the new solution
versions field:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466613
2.
It seems that there is a bug. If multiple solution
versions are specified, the additional details summary
block seems to only list only one eclipse version. From
the first one?
This is not a bug, it's currently designed to show the latest
information for the latest eclipse release that your listing is
compatible with. For example, if you have a solution version for
kepler and juno, the website should display information regarding
Kepler in the additional details summary block.
I created a bug to discuss this issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466612
I also created a bug to help us track the latest feature requests
and bugs for the next update of the Marketplace website and REST
api:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466611
Cheers!
From:
Konstantin Komissarchik [mailto:konstantin.komissarchik@xxxxxxxxxx]
Sent: Thursday, April 30, 2015 12:06 PM
To: 'Communication between MPC committers'
Subject: RE: [mpc-dev] New features for Eclipse
Marketplace and the Eclipse Marketplace Client
It’s
great to see this improvement. Two questions:
1.
How is backwards compatibility handled? If we have
separate solutions right now for different Eclipse
versions and we migrate to a single solution with multiple
variants, what happens when a Luna or a Kepler client
requests a listing?
2.
Has there been any thinking on migrating comments and
likes from existing solutions into the new merged
solutions? It would be a shame to lose all of that with
the transition.
Thanks,
-
Konstantin
Dear Marketplace Listing Owners,
We are very pleased to announce two new features for
Eclipse Marketplace and the Eclipse Marketplace Client
that will be part of the Mars release.
- The Eclipse Marketplace Client has been
improved to only display listings that are compatible
with the version of Eclipse the user is running. As a
Marketplace listing owner, you now have the ability to
create different versions of your listings, called
'Solution Versions', that are specific to the version of
Eclipse. For each Solution Version, you can specify an
update site, feature IDs, supported operating system and
supported version of Eclipse. The default for all
listings will be they are supported for all versions of
Eclipse.
- For your Marketplace listing, you can now
specify if a Feature ID is one of three conditions: 1)
Required, 2) Optional but selected by default, and 3)
Optional and not selected. We hope this will provide
more flexibility for you to specify the feature IDs that
are installed with Marketplace Client.
Both of these features will be available in the Eclipse
Mars release in June 2015. To prepare for Mars and these
new features we recommend the following:
- If your Eclipse listing is compatible with
all versions of Eclipse then you don't need to do
anything but we recommend you to have a look at your
listing's feature IDs and specify which are required or
optional.
- If your Eclipse listing is specific to a
version of Eclipse, please create a new Solution Version
in Eclipse Marketplace for each version. You can do this
today from your Eclipse Marketplace account.
Please let us know if you have any questions.
Regards,
Christopher Guindon
--
Christopher Guindon
Senior Web Developer
Eclipse Foundation
Twitter: @chrisguindon
_______________________________________________
mpc-dev mailing list
mpc-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mpc-dev
--
Christopher Guindon
Senior Web Developer
Eclipse Foundation
Twitter: @chrisguindon
_______________________________________________
mpc-dev mailing list
mpc-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mpc-dev
--
Ian Skerrett
VP of Marketing
Eclipse Foundation
(m) 613-240-7210
(o) 613-224-9461 ext 227
(t) @ianskerrett
|