The papyrus issue was apparently coincidence
before, since it re-occurred, so I have re-disabled that contribution.
This features has a dependency on
org.eclipse.e4.xwt 0.9.1 and as far as I know, e4.xwt is not
in Indigo, so .... ?
Via IM with Thomas, I have learned that
Buckminster does not plan on participating in Indigo, so I have removed
that contribution file.
I fixed the category problem for the
Sequoyah team ... the b3 aggregator editor really is necessary for making
category-type changes (and they promised to use it in the future :)
The current re-spin has passed verification
and is on to the mirror stage, so not too many things can go wrong now.
So, I think this run will be it for
M5 (unless someone asks for a restart real quick).
David M Williams/Raleigh/IBM@IBMUS
Cross project issues
02/03/2011 11:58 AM
Status and outlook for Indio M5
Ok, I'll try a respin soon. Details
below. Do any of these effect EPP packages? I will assume not ... if they
do, then we (i.e. you contributors :) will have to ask for a respin of
those packages as well (though I do not know their exact status).
word, from he who never changes his contribution file :) ]
not for M5]
mdt-papyrus.b3aggrcon [no word, but I'll try re-enabled first, since I
originally disabled for sequoyah not being there].
project issues <cross-project-issues-dev@xxxxxxxxxxx>
[cross-project-issues-dev] Status and outlook for Indio M5
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
We have fixed Sequoyah b3aggrcon file.
Could we have a respin, please?
EMF would like to request a respin to pick up our RAP contributions (I
forgot to re-enable them after RAP made their contribution).
On Thu, Feb 3, 2011 at 1:20 AM, David M Williams <david_williams@xxxxxxxxxx>
Technically, we should be done with M5, and I will assume we are, unless
someone makes a case for a respin. The main reasons I think we _might_
want to consider a respin, are that a) I did have to disable some sequoyah
features and the papyrus contribution at the last minute, to get a green
build, and suspect we are in a different timezones, since I've not heard
anything from them; and also that some features appear disabled that surprised
me and I wonder if someone just forgot to re-enable them? Or ... maybe
they meant to leave disabled? Should they be deleted from contribution
files?. The following contribution files have one or more features disabled.
Please check and comment if anything is amiss ... or, perhaps projects
just wanted to wait for M6 before re-enabling?
In any case, since we are past the +3 deadline, I have disabled. the Indigo
M5 aggregation builds, so please make a case if you have one (in particular,
please specify if anything is required for EPP packages?). I know
Markus will be building the final EPP M5 packages today (Thursday) so a
respin of repo may require a respin of EPP packages too?
I know it is a busy week ... with both M5 and SR2 RC2 ... which will be
my next note. :)