> > @Wayne, what's the official policy here?
It's the Planning Council's call. Is anybody from Eclipse BIRT paying attention to this thread? /bcc BIRT PMC, PL, and PC representative. Wayne On Wed, May 2, 2018 at 6:39 PM, Nick Boldt <[email protected]> wrote: > Maybe we need to consider removing BIRT 4.7.0 since it depends on versions > of requirements that are not in the Photon simrel. > > * DTP 1.13 version is 2 years old (Neon). > * WTP 3.9 version is 1 year old (Oxygen). > * EMF 2.13 is 1 year old (Oxygen). > > The fact that BIRT hasn't even done a milestone build since June 2017 [0] > means it might not even compile or run against these newer versions of its > dependencies. It might be fine, but it might not. No one has done the > diligence. > > [0] http://download.eclipse.org/birt/downloads/build_list.php > > I did find there's a 4.8.0 master branch build but those are *not running > tests*, and a new CI build hasn't been run since March 13, 2018 > (Photon.0.M6 +2 day) [1]. And it's still using WTP 3.9.0 (not 3.9.5 or > 3.10.0.M6) and DTP 1.13 (not 1.14). > > [1] https://ci.eclipse.org/birt/job/birt-master/60/ > > But if a project hasn't contributed new bits to the current simrel for M4, > M5, M6, despite having new CI builds... should it be removed like TM/RSE > was removed? The latest in simrel is 4.7.0.v201706, from the birt > oxygen-interim site [2]. > > [2] http://download.eclipse.org/birt/update-site/oxygen-interim/ > > @Wayne, what's the official policy here? > > On Wed, May 2, 2018 at 4:08 PM, Roland Grunberg <[email protected]> > wrote: > >> On Wed, 2018-04-18 at 16:42 -0400, Roland Grunberg wrote: >> > From the discussion in the bug [2], GMF, Papyrus, and Sirius are likely >> > to adopt the new version. Does BIRT, Graphiti, and TM4E intend to do so >> > as well ? The hope was to eliminate 1.6 and 1.7 entirely but given how >> > close this comes to M7, we might have to keep them in if adoption is >> > not possible for all projects. >> >> So after looking into the 2 remaining projects that haven't switched >> yet to Batik 1.9.1, It doesn't seem like they would be harmed by the >> removal of 1.6/1.7 from the Photon Orbit (active) build. >> >> - TM4E only has an optional dependency to Batik 1.7 or higher. The >> usage of Batik is limited to org.apache.batik.css.parser.Parser and >> between 1.7 and 1.9.1, this class did not change API or make any major >> modifications to that class. >> >> - BIRT is still using the R20170307180635 (Neon.3) Orbit build and is >> unlikely to switch for Photon. >> >> As a result I'll be removing Batik 1.6 & 1.7 from the Orbit active >> build. If anyone is opposed to such a move, or if issues arise, we can >> easily undo the change. >> >> Cheers, >> -- >> Roland Grunberg >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> > > > > -- > > Nick Boldt > > Senior Software Engineer, RHCSA > > Productization Lead :: JBoss Tools & Dev Studio > > IM: @nickboldt / @nboldt / http://nick.divbyzero.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > @ @redhatnews <https://twitter.com/redhatnews> Red Hat > <https://www.facebook.com/RedHatInc> > <https://www.facebook.com/RedHatInc> > > > “The Only Thing That Is Constant Is Change” - Heraclitus > -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
