On Wed, Mar 28, 2018 at 1:21 PM, Jamo Luhrsen <[email protected]> wrote:
> but, it's showing up as a dependency in the autorelease dependencies > log. Can/Should we just remove it entirely instead of just not building > it? > if it's not building I don't know how it is showing up in autorelease - unless maybe Daniel's query was from carbon. From oxygen on the -ui piece is not built. > > JamO > > On 3/28/18 1:14 PM, Sam Hague wrote: > >> netvirt has removed the building of the dlux ui feature already so >> archiving is fine with netvirt. >> >> On Wed, Mar 28, 2018 at 11:43 AM, Daniel Farrell <[email protected] >> <mailto:[email protected]>> wrote: >> >> Thanks for looking into that Daniel. I'll reach out to those projects >> to advise them that they should consider >> cutting their dependency on DLUX. >> >> I assume by your wording (and if I recall correctly, past >> discussions) that you're okay with archiving DLUX? >> >> Thanks, >> Daniel >> >> >> On Wed, Mar 28, 2018 at 11:28 AM Daniel Malachovský >> <[email protected]> wrote: >> >> Hi,____ >> >> __ __ >> >> Thanks for bringing this up. >> Unfortunately, i can’t attend meeting.____ >> >> __ __ >> >> Based of my searches, here is the list of projects with some GUI >> based on DLUX: >> >> ____ >> >> Bier____ >> >> Centinel____ >> >> dluxapps (it will die with DLUX as well probably)____ >> >> groupbasedpolicy____ >> >> honeycomb/vbd____ >> >> iotdm____ >> >> lispflowmapping____ >> >> nemo____ >> >> netvirt >> sdninterfaceapp >> systemmetrics >> unimgr____ >> >> usc____ >> >> __ __ >> >> I don’t know in which state those GUis are and if are still being >> used or not.____ >> >> __ __ >> >> dano____ >> >> __ __ >> >> *From:*Abhijit Kumbhare [mailto:[email protected] <mailto: >> [email protected]>] >> *Sent:* Tuesday, March 27, 2018 11:05 PM >> *To:* Daniel Farrell <[email protected] <mailto: >> [email protected]>> >> *Cc:* [email protected] <mailto: >> [email protected]>; tsc <[email protected] >> <mailto:[email protected]>>; >> [email protected] <mailto:[email protected]>; >> [email protected] <mailto:[email protected] >> ight.org>; Daniel Malachovsky -X (dmalacho - >> PANTHEON TECHNOLOGIES at Cisco) <[email protected] <mailto: >> [email protected]>> >> *Subject:* Re: [release] [OpenDaylight Discuss] [OpenDaylight >> TSC] DLUX Project status____ >> >> __ __ >> >> Added.____ >> >> __ __ >> >> On Tue, Mar 27, 2018 at 1:59 PM, Daniel Farrell < >> [email protected] <mailto:[email protected]>> wrote:____ >> >> Resurrecting an old thread, >> >> My understanding is that we're planning on archiving DLUX in >> Fluorine.____ >> >> __ __ >> >> If anyone objects to that, please speak up ASAP.____ >> >> __ __ >> >> @Abhijit - Can we add a vote on this to the TSC's agenda >> tomorrow?____ >> >> __ __ >> >> Thanks,____ >> >> Daniel____ >> >> On Sun, Feb 11, 2018 at 3:34 PM Robert Varga <[email protected] >> <mailto:[email protected]>> wrote:____ >> >> On 09/02/18 21:21, Abhijit Kumbhare wrote: >> > Daniel & DLUX project, >> > >> > Please note the TSC meeting minutes: >> > >> > https://lists.opendaylight.org >> /pipermail/tsc/2018-February/008836.html >> <https://lists.opendaylight.or >> g/pipermail/tsc/2018-February/008836.html> >> > >> > The consensus was that due to the lack of development >> resources - and >> > security vulnerabilities that there is a lack of >> bandwidth to fix - the >> > TSC thinks that it would be better to mark DLUX >> deprecated in Oxygen and >> > to remove it in Fluorine. What is your opinion on >> this? Do you have any >> > other suggestions or options? Ultimately it is the >> project's decision - >> > but do give it a thought and let us know. >> >> [+release, +discuss] as this boils down to a wider >> discussion. Do we >> need a UI framework, and if so, what do projects need >> from such a framework? >> >> Regards, >> Robert____ >> >> _______________________________________________ >> Discuss mailing list >> [email protected] <mailto: >> [email protected]> >> https://lists.opendaylight.org/mailman/listinfo/discuss >> <https://lists.opendaylight.org/mailman/listinfo/discuss >> >____ >> >> __ __ >> >> >> _______________________________________________ >> release mailing list >> [email protected] <mailto:[email protected] >> > >> https://lists.opendaylight.org/mailman/listinfo/release < >> https://lists.opendaylight.org/mailman/listinfo/release> >> >> >> >> _______________________________________________ >> release mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/release >> >>
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
