Actually I have done all of them except the following
208
1587
1709
1925
STP, ECF and GMF have to do something about those
Jeff
From:
orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx] On
Behalf Of Jeff McAffer
Sent: Monday, March 24, 2008 6:54 PM
To: 'Orbit Developer discussion'
Subject: RE: [orbit-dev] 20 Orbit CQs need attention
I have taken care of all the ones in the Eclipse project and
will update the ip log shortly
237 - 2195
256 - 2196
305 - 2197
1569 - 2198
299 - 2206
243 - 2199
293 - 2200
1065 - 2201
1116 - 2202
1153 - 2203
1232 - 2204
1367 - 2205
From:
orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx] On
Behalf Of David M Williams
Sent: Monday, March 24, 2008 3:20 AM
To: Orbit Developer discussion
Subject: [orbit-dev] 20 Orbit CQs need attention
I'm updated the Orbit build pages with a bit more information. For example, see
http://download.eclipse.org/tools/orbit/committers/drops/S20080324060456/
In the most recent builds from Orbit, you'll notice a link that says
IPZilla list
of all CQs
This is just a handy link to IPZilla querying CQ numbers that are listed in the
Orbit Iplogs.
If you click on and examine the list, you'll notice 20 that are incorrect.
That is, they are not Orbit CQs after all, but CQs for some other project.
All of our listed CQs should be orbit CQs, under the new rules (or, old rules
newly interpreted).
So .. if you are responsible for any of these bundles (see below) there two
courses of action.
1) Update IPLog. It might be there really is an Orbit CQ already, but just
hasn't been filled in the Orbit IP Log. If that's the case, just update the
IPLog.
2) Get an Orbit CQ. This is easier these days. If you go to the Eclipse
Portal, under your Project sections,
you'll see an "[add] an approved third-party library to Orbit"
link, that pretty much does everything for you, and should be quickly approved,
and then you can update the IPLog.
|