Re: [epp-dev] unable to provide M5 build - config.a.jre.javase

[Mickael Istria <mistria@xxxxxxxxxx>]

On Fri, Feb 2, 2018 at 9:21 AM, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> wrote:

Hi everyone,

Hi,

 

do you think it worthwhile to test at least upgrades to Photon M5 (from
M4, for example)?

I think it's worthwile testing upgrades from Oxygen.2 to Photon.M-latest. Testing upgrades from a milestone to another isn't really something we should spend too much effort on as it's not the typical scenario for end-users.

After all, <http://download.eclipse.org/staging/photon/> is there [1].
While this will not update the EPP plugins/branding, AFAICT most of the
package's functionality will be updated and thus can be tested -- even
if there is no package to vote on.

I believe the product version is locked (through a feature includes) to a specific version of Platform feature -and vice-versa, the Platform feature version in locked by the depedency to this specific version from product. So even if the upgrade from update site would upgrade most of the components, it most likely wouldn't upgrade the product definition nor the Eclipse Platform feature.

Not testing latest Platform feature as part of the upgrade is a major issue.