Thank you for providing the workaround. It looks good to me and I would push it as soon as I verified the results from the verification job.
How do we proceed from here? I suggest the following:
*TODAY*
- Wait for the verification job and verify that is a valid workaround that solves the problem in M4 and does not introduce any unwanted side effects.
- Publish the M4 packages that received a +1 as planned today, hold back those that got a -1
- Do not enable the EPP p2 repository with the M4 version of the packages today
*BEGINNNG OF NEXT WEEK*
- Create an M4a based on the workaround
- Publish M4a packages for those with a -1 in M4 (probably on Tuesday, Wednesday at the latest depending on mirror servers and package maintainers)
- Enable the M4a EPP p2 repository together with the M4a packages
Current voting status:
? C/C++
+1 Java, Modeling, Android, DSL, Testers, Automotive, RCP/RAP
-1 Parallel
Does anyone have any objections? Or better proposals? If I don't hear any objections until, let's say 11am eastern I'd move on as proposed.
Thanks and regards,
Markus
To change your delivery options, retrieve your password, or unsubscribe from this list, visit