[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [rt-pmc] Swordfish Release
|
I am resending this note as I have now actually subscribed to the rt-dev
mailing list.
--
The EMO, for one, will start digging deeper during release reviews.
FWIW, the 0.8.0 download also appears to contain some libraries for
which I cannot find CQs.
Tooling sounds like a good idea. I'm not sure how we marry the CQ to the
JAR, but it is worth exploring.
Wayne
Thomas Watson wrote:
I'm fine with waiting until EOB today.
What can be done to prevent this situation in the future? Perhaps some
tooling would help catch third party jars in the build that are not
approved by the IP team?
Tom
Inactive hide details for Jeff McAffer ---06/29/2009 09:07:43 AM---My
mailer was hiding this message when I made my previous reJeff McAffer
---06/29/2009 09:07:43 AM---My mailer was hiding this message when I
made my previous response...
From:
Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>
To:
Runtime Project PMC mailing list <rt-pmc@xxxxxxxxxxx>, Mike
Milinkovich <mike.milinkovich@xxxxxxxxxxx>, emo-ip-team@xxxxxxxxxxx,
Wayne Beaton <wayne@xxxxxxxxxxx>, Eclipse Management Organization
<emo@xxxxxxxxxxx>
Date:
06/29/2009 09:07 AM
Subject:
Re: [rt-pmc] Swordfish Release
------------------------------------------------------------------------
My mailer was hiding this message when I made my previous response...
Thanks for the clarification Oliver.
>From the PMC point of view, this is fine. We do not speak for the IP
team however and will defer to their risk assessment.
There is some question about the testedness of the release. For
example, what was being tested prior to the release? What will have
been thoroughly tested after the changes you propose here? As
Swordfish is in incubation these concerns are not primary but it is
still a topic to consider.
Jeff
Oliver Wolf wrote:
Dear RT PMC Members,
since this issue cannot wait until the July 15th, I’d like
to give you an update on the current state of affairs:
The Swordfish project is currently investigating the
gaps/discrepancies regarding IP compliance in depth.
It turns out that most of the third party contributions
that have accidentally been included in the release
without proper IP clearance can actually be removed
without any impact on functionality. They have been pulled
in as downstream dependencies of other 3rd party libs, but
are purely optional and not critical for our purposes.
Fortunately, these include the ones considered critical by
the IP team (cglib, staxex, stax2).
There are, however, some contributions remaining which are
needed and don’t have corresponding CQs. Odds are good
that these are exclusively originating from Apache
licensed projects hosted at the Apache Foundation and can
probably be considered comparatively low risk.
We’re going to provide the findings of our investigation
to the PMC for your attention by EOB today. If there are
no objections from your side, we can further discuss the
next steps here on the mailing list. If you feel that a
phone conference would be more appropriate, please suggest
a time and we’d be happy to accomodate.
Regards,
Oliver
Am 29.06.09 11:45 schrieb "Christian Campo" unter
_<christian.campo@xxxxxxxxxxxx>_
<mailto:christian.campo@xxxxxxxxxxxx>:
Hi Ricco,
the plan was to skip the next RT PMC Call and
the next planned one is on the 15th of July.
christian campo
Am 29.06.2009 um 11:37 schrieb Ricco Deutscher:
RT PMC,
May I suggest to use the next RT
PMC call for a presentation by
Oliver as the Swordfish project
lead. The presentation should
address the following questions:
# What is the level of
discrepancy?
# What are the root
causes for these
discrepancies?
# What are the measures
the PL suggests to the
PMC?
#
Is it correct, that the next RT
PMC call takes place on Wednesday,
July 1st at 9am EST/3pm CET?
Any comments or additions?
Best,
Ricco
Am 29.06.09 02:51 schrieb "Mike
Milinkovich" unter
_<mike.milinkovich@xxxxxxxxxxx>_
<mailto:mike.milinkovich@xxxxxxxxxxx>:
RT PMC,
It has come to the
attention of the EMO
that there are
discrepancies between
the list of
third-party packages
listed by the
Swordfish project in
its Release Review
documentation and
their filed CQs and
what is actually
shipping with their
release. The EMO would
like the PMC’s
concurrence to
removing this release
and revoking
Swordfish’s Release
Review until these
discrepancies are
addressed.
I am on vacation this
week, if you have any
questions please use
Wayne Beaton as your
EMO point person on
this issue.
Thanks.
Mike Milinkovich
Executive Director
Eclipse Foundation, Inc.
Office:
+1.613.224.9461 x228
Mobile: +1.613.220.3223
_mike.milinkovich@eclipse.org_
<mailto:mike.milinkovich@xxxxxxxxxxx>
blog:
_http://dev.eclipse.org/blogs/mike/_
twitter: @mmilinkov
<ATT00001.c>
*
Oliver Wolf*
Lead Architect Runtime Platform
Tel.: +49 228-182 19059
Fax: +49 228-182 19193
Mobil: +49 160-98931313_
__oliver.wolf@sopera.de_ <mailto:oliver.wolf@xxxxxxxxx>
Wussten Sie schon? *SOPERA*
<_http://www.osbf.de/de/node/1466_> hat den Open Source
Business Award 2009 <_http://www.osbf.de/en/node/1466_>
verliehen bekommen!
*
SOPERA GmbH - Open Source SOA*
Subscription Services, Support & Maintenance, Training,
Technical SOA Consulting & Customized Development*_
_**_www.sopera.de_* <http://www.sopera.de/>*
<**_http://www.sopera.de/_**>
*
SOPERA GmbH · Geschäftsführer: Dr. Ricco Deutscher, Harald
Weimer, Peter Spiegel
Sträßchensweg 10 · 53113 Bonn · Handelsregister: Bonn HRB
15336
Hohenlindnerstraße 11b · 85622 München
Vertraulichkeitshinweis: Diese Nachricht und jeder
übermittelte Anhang beinhaltet vertrauliche Informationen
und ist nur für die Personen oder das Unternehmen
bestimmt, an welche sie tatsächlich gerichtet ist. Sollten
Sie nicht der Bestimmungsempfänger sein, weisen wir Sie
darauf hin, dass die Verbreitung, das (auch teilweise)
Kopieren sowie der Gebrauch der empfangenen E-Mail und der
darin enthaltenen Informationen gesetzlich verboten ist
und gegebenenfalls Schadensersatzpflichten auslösen kann.
Sollten Sie diese Nachricht aufgrund eines
Übermittlungsfehlers erhalten haben, bitten wir Sie, den
Sender unverzüglich hiervon in Kenntnis zu setzen.
------------------------------------------------------------------------
_______________________________________________
rt-pmc mailing list
_rt-pmc@eclipse.org_ <mailto:rt-pmc@xxxxxxxxxxx>
_https://dev.eclipse.org/mailman/listinfo/rt-pmc_
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc