[cross-project-issues-dev] Eclipse Project to be a bit late with RC4 con

[David M Williams <david_williams@xxxxxxxxxx>]

Up until an hour ago, we were all set with
having our final build 
for 4.2.1
http://download.eclipse.org/eclipse/downloads/drops4/M20120912-1200/

and 3.8.1 would have been
http://download.eclipse.org/eclipse/downloads/drops/M20120905-1000/

But, some last minute discussion deemed
the two bugs below to be so serious for some adopters/environments, that
if we did not respin SR1, we would have to provide an "update site"
with patches for those fixes. The decision was made that a respin would
be easier for everyone. 

Bug 383890
- JVM (Eclipse) crash with SIGSEGV in ld-linux-x86-64.so.2 
Bug 381407
- reproducible crash in Debug's Variables view 


I have updated our contribution in the ep and equinox
b3aggrcon files to M20120912-1200
as our "near RC4" contribution and have re-enabled the aggregation
build job. 

Our project rebuild (with unit tests)
will be complete on Saturday and I plan to update to the contribution file
over the weekend to what will presumably be our final build unless something
looks off. 

BUT, technically speaking, we won't
officially declare that as our final RC4 build until the SWT team has a
chance to confirm and verify on their collection of platforms, which won't
happen until some time on Monday. 

I do not plan to announce "done
with final RC4" on Monday so if you don't hear otherwise assume we
are done; as I'm 99% sure the weekend build will be great. But, if you
need a more positive confirmation, you can watch our sign-off bug 
Bug 389444
- Declare Juno SR1 RC4 

In case you are wondering, this rebuild should not require
anyone to rebuild their own stuff, and even testing should be unaffected
unless you are in one of those "sensitive environments" (and
then you might want to re-test to make sure the patches got in, and your
crashes no longer occur ... and I know some of that has been going on already.


Sorry for any inconvenience caused by this late decision.

But greatest thanks to all those involved in finding,
reproducing, fixing, and testing those two very difficult bugs. Bug 383890
especially is a "5 stars" bug if I ever saw one. :)