The Platform cannot
envision all the ways it is used. We do what we can to test. So, as long
as you test your stuff against all the milestones and then don't file bugs
after RC2 - fine.
Watson <g.watson@xxxxxxxxxxxx> To:
Megert <daniel_megert@xxxxxxxxxx> Cc:
Cross Project Issues <cross-project-issues-dev@xxxxxxxxxxx>, eclipse.org-committers@xxxxxxxxxxx Date:
Re: [cross-project-issues-dev] [eclipse.org-committers] Use
Milestones/RCs To Test and Run Sent
Projects have enough on their plates
testing their own code, let alone testing the platform. This seems to be
a deficiency in the regression testing of the platform, and should be handled
by the platform team IMHO.
It would be great
if everyone could at least test or even better, run on the latest milestone/RC.
Platform got a stop ship bug for 4.13 and one for 4.14 reported after RC2.
The 4.13 bug was introduced in M3 and the 4.14 bug in M1. So, there would
have been enough room to find the bugs earlier. Of course the Platform team does exactly that but everyone has its own
patterns how to work and hence, unfortunately did not detect those bugs. Thanks to everyone who helps with testing! Dani _______________________________________________ eclipse.org-committers
mailing list eclipse.org-committers@xxxxxxxxxxx https://www.eclipse.org/mailman/listinfo/eclipse.org-committers
IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation. To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal. _______________________________________________ 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev