Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] New M6 plan -- slipping one day, to Wednesday 3/30 10 AM

Given the serious nature of the previously mentioned issues, we have decided to re-spin the Sim. Release repo, and EPP packages.

The new 'staging' repository will not be ready for several more hours, and EPP packages should be ready for (re) evaluation Tuesday morning.

Assuming no other blocking issues are found, we will promote that as the M6 delivery on Wednesday, 3/30, approximately 10 AM.

I will update the following bug at every stage of the process.
Bug 490550- Re-spin M6 candidate repository


From:        David M Williams/Raleigh/IBM@IBMUS
To:        cross-project-issues-dev@xxxxxxxxxxx,
Date:        03/28/2016 05:41 PM
Subject:        [cross-project-issues-dev] Heads up: we may delay M6 Sim. Release        again.
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

A pretty serious issue has been found, where one project (or, the interaction of a few) causes some project's M6 content to not be in the SIm. Release repository (but instead "back leveled"  at least WTP, or part of WTP? to the M5 level).

For more detail, see

This is still being investigated, and we are waiting to hear back from some projects. But I wanted to give a "heads up" since to re-spin (one way or another) is the only solution I know of.

I'll update this list once I know a solid plan, but, in the mean time, I will start a "pessimistic" respin, that simply excludes a few projects. Ideally, we can get some quick fixes that might make that pessimistic respin unnecessary, and then would do another "more correct" respin.

Stay tuned ...


cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top