[wtp-dev] Status and outlook of our march to M4

[David M Williams <david_williams@xxxxxxxxxx>]

Most importantly,  it turns out
there is no way to get an "official" update of JEM until, Jan
2 or 3, at earliest ... so, we can not officially declare M4 until Jan.
4, at the earliest. 
(That is, we will not be declaring anything
early, as we were hoping, but there is still a chance of making our original
committed date). 

There is a good chance we can figure
out how to patch JEM ourselves, and get a version that is worthy of "milestone
testing". 
But I am still working on "gutting
this into our build" in the correct way, but am not there yet. I'll
likely have an updated status Sunday evening. 
In the meantime, if anyone want's to
kick tires, you can use our current I-builds, but add the patched jar that
is attached to bug 167992. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=167992

So, I would consider us on a day-to-day
slip of starting any milestone testing. There's some good indications that
our patching efforts will be successful for main paths, 
but appears there's plenty of other,
or possibly side effect issues as well. (many thanks to Kathy for her early
testing, see bugs 168285 and 168285). 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=168285
https://bugs.eclipse.org/bugs/show_bug.cgi?id=168286

Do be sure to use the "pre-reqs"
listed on the build page, and, infact, for your development environment
be sure to move up to the official M4 version of the platform, it's test
framework, and releng tool. 

As always, let us know if questions
or concerns, 

David