Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] [cross-project-issues-dev] Announcing the BIRT project's intent to participate in Release 2019-06
Benjamin/Denis, I've reached out to the people directly and communicated the issues raised in this thread. I've also provided a link this thread. I'll report back as soon as I hear. 

-Gunnar

-- 

On May 13, 2019, at 05:58, Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx> wrote:

+1 on doing something, _anything_ about BIRT. Some of their vulnerabilities are just nasty.

Then there's the perception that bugs just go into /dev/null...

https://bugs.eclipse.org/bugs/show_bug.cgi?id=546816


Denis


On 2019-05-10 8:41 p.m., Benjamin Cabé wrote:
Hi,

Not sure if this belongs to the AC but I do think to some extent it does. I've been on the security@ mailing list for a number of years and I can't remember one single time where the BIRT project team has engaged w.r.t to the security vulnerabilities that are regularly reported. 
How do we feel about shipping a simrel with numerous known vulnerabilities?


Benjamin

---------- Forwarded message ---------
De : Mihail Mihaylov <mmihaylo@xxxxxxxxxxxx>
Date: ven. 10 mai 2019 à 12:28
Subject: [cross-project-issues-dev] Announcing the BIRT project's intent to participate in Release 2019-06
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: Juan Fernandez <juanf@xxxxxxxxxxxx>, Virgil Dodson <vdodson@xxxxxxxxxxxx>, John Ward <jward@xxxxxxxxxxxx>


Hi All,

 

Per the SimRel/Simultaneous Release Requirements, we are announcing the BIRT project's intent to participate in Release 2019-06. Apologies that this was not done before the milestone 1 (M1) date of the release.

 

Our plan is to touch the project's aggrcon file today (the milestone 2 date).

 

Thanks,
Mihail

 

P.S. We ran into challenges with the new build process requirements (https://bugs.eclipse.org/bugs/show_bug.cgi?id=532136), but feel we can comply with these in a timely fashion on our side.

 
 
_______________________________________________
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-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-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-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-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.

Back to the top