[cross-project-issues-dev] Final Daze for Indigo SR1

[David M Williams <david_williams@xxxxxxxxxx>]

We do not have a separate document for
"final daze" for maintenance, but the same principles apply,
so you (especially project leads and release engineers) may want to review
those principles in 

http://wiki.eclipse.org/Indigo/Final_Daze

And if any questions, please ask. 

In particular, some of the most significant
things are

1. This week is our final build(s) even
though called "RC4". Thursday, 9/15, 5 PM Eastern is the last
possible time to contribute something to Indigo SR1. Anything after that
will need to be in Indigo SR2, or provided from your own projects download
site or software repository. [There can be exceptions, causing a rebuild
to be justifiable, but a "bad bug in our code" is usually not
sufficient ... it needs to be something that effects multiple projects,
causes installs or updates to fail, etc. ... things that can not be solved
by a project's own patches or updates]. If you contribute anything after
your designated +n day, please let us all know here, so potentially effected
projects will know if they need to rebuild or retest anything. 

2. You should not announce or provide
your own projects final downloads "to the general public" until
the Simultaneous Release date, Friday 9/23. This is to give a "quiet
week" to do final preparation, testing, and mirroring. But, do put
your downloads and repositories in a position to be mirrored, just leave
them "invisible".  There is a FAQ on "how to make your
build invisible" [1] in case anyone needs a "how to" reminder.
[Some projects may have other procedures ... the FAQ just covers some possible
methods.]

3. As a special case of '2', the final
EPP packages (for RC4, this week, due Friday) will not be viewable to "downloads"
since that is what happens when they are released, and we do not want to
pre-release the final bits. They will be available in their usual EPP locations
for final testing. 

4. The common repo will (continue) to
be in .../releases/maintenance, but then next week on the release day,
9/23, it will be combined as a composite with .../releases/indigo. There
is a FAQ with some high level "how to" instructions on how to
test a pseudo composite [2] and its strongly recommended teams test that
pseudo composite, to simulate what end-users will encounter after the release.


So, I hope everyone (who needs it) is
getting their shell accounts restored, and we can finish up stress free
this week. 

There are currently 3 blocking problems
(that I know of): 

This first one is preventing the aggregation
build from running:  

357171
 Cross-Pr --- org.eclipse.emf.teneo.hibernate.libraries included when
it should not be

These two just have to do with some legal file issues
which are not preventing builds, but, I think, are required for release


357168 Papyrus ---
many missing about.html files 
357170  cdt-rele
--- a couple license files missing 


Thanks, 


[1] http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#How_is_a_final_build_made_.22invisible.22_until_release.3F

[2] http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#Test_staging_as_a_pseudo_composite