[cross-project-issues-dev] Last day for Juno SR1 contributions

[David M Williams <david_williams@xxxxxxxxxx>]

Here we are already, Juno SR1 RC4 +3. 

I did have to temporarily disable Jubula
to get a green build but I know they are working on the issue, if not fixed
already. 

5 PM today, Wednesday, (Eastern) is
the deadline, unless someone speaks up that they need a few extra hours.


And then we begin "quiet week".
This is a good time for committers and adopters to do some final testing.
Even if a bad bug or regression was found, and could not be fixed in "common
repo" due to being too late, projects can always produce their own
update sites with patched features, or work on documenting workarounds.
 Better to know ahead of time, than be surprised. Remember, any requests
for respins need to go through the formal exception process, and it has
to be something pretty big that can not be fixed by a normal patch feature,
or similar. 

While there is no formal "Final
Daze" document for service releases, it would be good for simrel engineers
to review the main one for Juno, at 
http://wiki.eclipse.org/Juno/Final_Daze

The principles are the same ... clean
up old stuff so mirrors don't get full. Promote zips and repositories early
to make sure they get well propagated to mirrors but "leave invisible"
until Friday, 9/28, so we do not prematurely "release" anything
before its time, in an uncoordinated fashion that's confusing to end-users
(if not the rest of us). 

Don't forget, if any of you changed
or fixed substantial parts of your "help docs", you may want
to open a bug in cross-project list to have webmasters update the info
center for Juno SR1. 

Lastly, remember to change the repository
reports ... I still see one missing "about.html" file .... 
http://build.eclipse.org/simrel/juno/reporeports/

Thanks everyone,