Carl,
The MPC Luna project plan was published on this mailing list on Jan
12, 2015.
https://dev.eclipse.org/mhonarc/lists/mpc-dev/msg00386.html There
have been bugs open before that date concerning the main features.
Updates have also been posted on the mailing list and I would invite
you to view them in the archive. I am not sure how we could
communicate more about the changes?
I am sorry this puts you in a bad situation. I would suggest you
open bugs for each of your concerns and we will try to address them.
FWIW, if someone is using the Helios version of MPC then nothing
should have changes for them. You might have been specifying the
exact version information but that information was never used by
MPC.
Regards
Ian
On 04/05/2015 6:09 PM, Carl Anderson
wrote:
Christopher,
This really puts my product in
a bad situation... the biggest issue is lack of communication.
With no warning, suddenly all of the version information that
we had was lost. Our Helios version now shows that it is
supported on all versions including Mars, and our Luna version
shows that it is supported on all versions all the way back to
"previous to Juno". We had exact versions supported listed
out before, but all of that was lost.
On top of that, we can't just
quickly update all of the entries with the appropriate
versions and save- the features have been reworked... and
while it is nice to have options as to specifying required,
optional-selected, and optional, there now must be at least
one required feature, which makes this a decision-making
process needing review instead of just a quick update.
And, to add to the churn, we
really should collapse a lot of our entries into one, and then
just have Solution Versions. That is great for new
Marketplace Entries, but we do lose information (including
comments, likes, and install history) if we collapse our
entries down. Konstantin brought this up already in a
separate note, so I won't belabor the issue here.
So, the main questions: what
else will be changing for Mars? Can we have better
communication of upcoming major changes before they are
released? And what testing has been done with the web site
and with older versions of Eclipse (and its Marketplace
Client) to make sure that everything works there? (And along
those same lines, what testing do we need to do to verify that
whatever changes we make for our current Eclipse Marketplace
entries still work?)
One last note along these
lines- we have listings in the Eclipse Marketplace for both
Beta versions of our product and released versions. Up until
these changes, they were easy to distinguish, since the
version was shown as part of the results on the Eclipse
Marketplace. Now, the version is no longer shown. We are
considering changing the names of the betas to include the
word beta- are there more upcoming changes? Or are we safe to
go ahead and do this? (Since we would not want both the word
beta in the name and the version to suddenly appear in our
listings.)
FWIW,
- Carl Anderson
WDT co-release engineer
 Christopher Guindon ---04/30/2015
01:49:16 PM---Dear Marketplace Listing Owners, We are very
pleased to announce two new features for Eclipse Market
From: Christopher Guindon
<chris.guindon@xxxxxxxxxxx>
To: mpc-dev@xxxxxxxxxxx
Date: 04/30/2015 01:49 PM
Subject: [mpc-dev] New features for Eclipse
Marketplace and the Eclipse Marketplace Client
Sent by: mpc-dev-bounces@xxxxxxxxxxx
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.
1. 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.
2. 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:
1. 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.
2. 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
_______________________________________________
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
|
