Re: [cross-project-issues-dev] Status and outlook for Kepler M4 at end o

[David M Williams <david_williams@xxxxxxxxxx>]

Thanks for letting us know. 

I pointed out jwt because the whole
"contribution" was disabled, not merely its repos or features.
That "disabled contribution" was the "start state"
for Kepler and I asked teams to enable their contribution if/when they
wanted to participate in Kepler (even if they had to disable their repo
or feature temporarily). 

Perhaps I, or someone, mistakenly disabled
your whole contribution after it had been enabled for Kepler. If so, sorry
about that. But, if I'm looking at Git history correctly, it has not been
touched for 4 months. 

So, yes, the deadline for M4 is ASAP.
Wednesday, tomorrow, 12/19: it is the +3 day ... the last day to make contributions
for M4.  (which is Friday, 12/21).

So, re-enable if you are participating
in Kepler and/or update to your "current" Kepler builds. 

Not to mention ... this applies to everyone,
of course, ...  subscribe to cross-project list, cross-project bugs,
and get familiar with all the requirements and deadlines in the various
documents at 
http://wiki.eclipse.org/Kepler

Thanks again, 





From:      
 Marc Dutoo <marc.dutoo@xxxxxxxxxxx>
To:      
 David M Williams/Raleigh/IBM@IBMUS,
cross-project-issues-dev@xxxxxxxxxxx, "'Christian Saad'" <christian.saad@xxxxxxxxxxxxxxxxxxxxxxxxxx>,

Cc:      
 Mickael Istria <mistria@xxxxxxxxxx>
Date:      
 12/18/2012 04:35 AM
Subject:    
   Re: [cross-project-issues-dev]
Status and outlook for Kepler M4 at end of +1

---

Hi David

Eclipse SOA's JWT project here...
Obviously we'd want to stay in the Kepler release train !!

I guess for that we'd have to get your "green" build, solve whatever
problems JWT has with it, make our own build work, and then put back enabled="true"
in jwt.b3aggrcon in the simrel git project (*), am I right ?

And what deadline would there be for that ? (ASAP I suppose, but you know
this period of the year...)

I'm putting our release engineer Chris in cc.

And thanks to Mickael for pointing that out !

Regards,
Marc Dutoo
Eclipse JWT co-lead
Open Wide

(*) http://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build


-------- Original Message --------

Subject:	[cross-project-issues-dev] Status and outlook for Kepler M4 at end of +1
Date:	Mon, 17 Dec 2012 17:20:28 -0500
From:	David M Williams <david_williams@xxxxxxxxxx>
Reply-To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
To:	Cross project issues (cross-project-issues-dev@xxxxxxxxxxx) <cross-project-issues-dev@xxxxxxxxxxx>

We finally got a green build! Though, I did have to disable a few things,
either there was a conflict, such as for ICU4J v50 vs 4.2, and many others
because something else was disabled. 

There's the current status of enabled flag: 

Whole contribution disabled ... never enabled for Kepler. I'll remove these
if I don't hear something soon. 

emf-query2.b3aggrcon - org.eclipse.simrel.build 
jwt.b3aggrcon - org.eclipse.simrel.build 


These have a feature or repository disabled, some disabled by "owners",
since they knew they needed some work still, and a few disabled by me,
based on what I could see using the b3 aggregator editor's "validate
aggregation" function. Feel free to re-enable if/when you think ready.

amp.b3aggrcon - org.eclipse.simrel.build 
birt.b3aggrcon - org.eclipse.simrel.build 
dltk.b3aggrcon - org.eclipse.simrel.build (2 matches)
egit.b3aggrcon - org.eclipse.simrel.build 
gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build (2 matches)
mat.b3aggrcon - org.eclipse.simrel.build 
mdt-papyrus.b3aggrcon - org.eclipse.simrel.build 
mmt-qvto.b3aggrcon - org.eclipse.simrel.build 
soa-bpel.b3aggrcon - org.eclipse.simrel.build 
webtools.b3aggrcon - org.eclipse.simrel.build 

I've promoted what we had from this first green build to .../releases/staging.

Don't forget to check the reports occasionally: 
http://build.eclipse.org/simrel/kepler/reporeports/

Thanks,