Dani,
I also double checked in any EPP package repo to see if any has a
reference to any birt namespace, and they don't. So if the
aggregation validates, then the necessary (and identical )
requirements are on the train.
Regards,
Ed
On 09.12.2019 15:56, Ed Merks wrote:
Dani,
No, it's in the same bad state it's been in since oxygen and
while they did another relase, they did not contribute it to
simrel; or did and then reverted it.
But the downstream consumers on the train only have bundle
dependencies so those bundles remain the same...
Regards,
Ed
On 09.12.2019 14:23, Daniel Megert
wrote:
Hi Ed
Is BIRT
causing a regression in 4.14 or was it in the same state in
4.13? If the latter, I'm a bit concerned to do this in RC2.
Dani
From:
Ed
Merks <ed.merks@xxxxxxxxx>
To:
cross-project-issues-dev@xxxxxxxxxxx
Cc:
Eclipse
Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>
Date:
09.12.2019
12:51
Subject:
[EXTERNAL] Re:
[eclipse.org-planning-council] [cross-project-issues-dev]
Restrict BIRT's Contribution...
Sent by:
eclipse.org-planning-council-bounces@xxxxxxxxxxx
Folks,
I'll give the BIRT team until the end of today take respond
and/or take
action, and failing that, I think it best that I take
"executive action"
and limit BIRT's contribution to the feature needed by the
train's
downstream consumers. It's also probably best to do as Ed
suggests,
I.e., remove the BIRT custom category as well because I have
no idea
what user-level functionality is provided by this small
feature.
If anyone has concerns or objections, please speak up as
soon as
possible, because tomorrow I'll take action.
Regards,
Ed
On 07.12.2019 11:50, Ed Willink wrote:
> HI
>
> On 07/12/2019 09:39, Ed Merks wrote:
>>>
>>> Therefore surely all BIRT features should be
removed from all SimRel
>>> categories?
>>>
>> I took the approach of minimizing the impact,
leaving this charting
>> feature in the category. I think that's least
disruptive at this point.
>
> The BIRT chart feature would still be there for those
who explore the
> uncategorized view and of course for transitive install
by consuming
> projects such as MoDisco.
>
> No BIRT feature would be there to fool users into
believing there is a
> BIRT tool.
>
> For MoDisco it appears that total loss of BIRT would
just require an
> optional feature to be removed. Since that feature
enables BIRT charts
> to be modelized and BIRT is missing, retaining the
feature presumably
> only supports rescue of legacy BIRT charts.
>
> Regards
>
> Ed
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your
password, or
> unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes
internal to the Eclipse Foundation. To be permanently
removed from this list, you must contact emo@xxxxxxxxxxx
to request removal.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
|