[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mpc-dev] Remediation support and MPC target platforms
|
I hope early next week. I am very worried about introducing a new capability
this last in the development cycle.
One idea to limit the risk would be to move to Kepler only support for MPC
1.2 in June and then add the remediation capability for SR1.
Thoughts?
-----Original Message-----
From: Pascal Rapicault [mailto:pascal@xxxxxxxxxxxxx]
Sent: May-08-13 5:47 PM
To: Ian Skerrett; Communication between MPC committers
Subject: Re: [mpc-dev] Remediation support and MPC target platforms
Ian, any ETA on when you will make a final decision on this?
On Wed, May 8, 2013 16:17, Ian Skerrett wrote:
> Lets go with #1 for M7.
>
>
> Sent from Samsung Mobile
>
> -------- Original message --------
> From: Carsten Reckord <reckord@xxxxxxxx>
> Date:
> To: Communication between MPC committers <mpc-dev@xxxxxxxxxxx>
> Subject: Re: [mpc-dev] Remediation support and MPC target platforms
>
> Ian,
>
> How would you like to proceed for M7? As I see it, the options are
>
> 1) ship M7 as-is, without remediation, and discuss anything further
> for
> RC1
> 2) include Remediation using reflection to maintain Helios
> compatibility and remove the compatibility code later if we switch to
> Kepler-only
> 3) make the move to Kepler-only now and merge the Remediation support
> as-is
>
> I've already kicked off a build with all other changes for the
> aggregator to pick up, just to be safe. So 1) is pretty much "do
> nothing now".
>
> I have local changes ready with the refactorings for 2), so that's
> still doable for M7, too.
>
> And 3) would just be throwing the switch on Gerrit to merge
> Remediation and doing a rebuild.
>
>
> On 07.05.2013 22:36, Ian Skerrett wrote:
>> I am hoping Steffen and Benjamin might comment on any historical
>> reason for the backward compatibility requirements. I would tend to
>> think that people using the Kepler version of MPC will be using it
>> with Kepler. However, I might be missing a use case?
>>
>> Benjamin and Steffen any thoughts?
>
> _______________________________________________
> mpc-dev mailing list
> mpc-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mpc-dev
>
> _______________________________________________
> mpc-dev mailing list
> mpc-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mpc-dev
>
