|[eclipse.org-planning-council] Fwd: [cross-project-issues-dev] Severe regression in PDT Neon.3 RC4 - chance for a respin?|
Greetings Planning Council.
We have a request for a respin. As we are technically in the quiet "week", your approval is required.
Please voice your concerns. If you have any technical questions, it's probably better for you to ask them either on the bug or on the cross-project-issues-dev mailing list where Kaloyan will be able to see them and respond.
Since it's pretty late in Europe (where our release engineering folks live), the actual release engineering aspects of a respin will have to wait until next week.
Please vote +1, 0, -1.
-------- Forwarded Message --------
While testing the PHP EPP Neon.3 RC4 we found a severe regression . While it does not affect the Simultaneous Release as a whole, it is something that would affect most of the PHP users.
I know the simplest and risk free solution is PDT to have a maintenance release on the date of the Neon.3 release train. But, as the affected workflow is one that would be executed early after starting the IDE, most probably, the affected users would not notice that there is a maintenance update they need to apply. The effect of freezing the IDE would result in a very negative experience with the Eclipse IDE.
For the above reasons, I'd like to ask what are our chances for respinning the Neon staging p2 repo?
Technically speaking, we need to revert one patch in PDT and release a RC5 milestone. Then the Neon staging p2 repo needs to be respun and then the EPP packages.
The Eclipse Foundation
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev