I think the options are the following ones: Option 1: Deprecation notice in Carbon Removal in Nitrogen
Option 2: Deprecation notice in Carbon Adaptation in Nitrogen Removal in Oxygen Option 3: Deprecation notice in Nitrogen Adaptation in Oxygen Removal in Fluorine Or Option 4 … being whatever we could thing of. During the kernel meeting I was more after option 3, but I think option 2 make sense so downstream consumer can be notified earlier in the process and start migrating things to blueprint. Thanks, Alexis > On Nov 15, 2016, at 3:47 PM, thomas nadeau <tnad...@lucidvision.com> wrote: > > I also thought we had an official project policy for deprecating functions > only after several major releases to avoid the scenario Brian describes. > > tom > > > On Nov 15, 2016, at 12:20 PM, FREEMAN, BRIAN D <bf1...@att.com > <mailto:bf1...@att.com>> wrote: > >> It seems like you need at least one release for deprecation before removing >> a function. I know I have code that uses the Config subsystem so it would be >> a real pain to move in one release and creates an upgrade nightmare for me >> that would slow down my migration to Carbon. >> >> Brian >> >> >> From: controller-dev-boun...@lists.opendaylight.org >> <mailto:controller-dev-boun...@lists.opendaylight.org> >> [mailto:controller-dev-boun...@lists.opendaylight.org >> <mailto:controller-dev-boun...@lists.opendaylight.org>]On Behalf Of Colin >> Dixon >> Sent: Tuesday, November 15, 2016 12:14 PM >> To: controller-dev >> Subject: [controller-dev] deprecating the config subsystem in Carbon? >> >> During last week's Kernel projects call [0], I asked if and when we wanted >> to deprecate the config subsystem. During the conversation, I think everyone >> agreed that we should strongly discourage people from building new projects >> based on it and encourage people to move toward Blueprint, which sounds like >> the definition of deprecation. >> >> There was also seeming consensus that actually removing it in Carbon might >> be a bad idea. Especially without a lot of effort. >> >> What are people's thoughts? >> >> Cheers, >> --Colin >> >> [0] >> https://meetings.opendaylight.org/opendaylight-meeting/2016/kernel_projects/opendaylight-meeting-kernel_projects.2016-11-08-17.05.html >> >> <https://meetings.opendaylight.org/opendaylight-meeting/2016/kernel_projects/opendaylight-meeting-kernel_projects.2016-11-08-17.05.html>_______________________________________________ >> controller-dev mailing list >> controller-dev@lists.opendaylight.org >> <mailto:controller-dev@lists.opendaylight.org> >> https://lists.opendaylight.org/mailman/listinfo/controller-dev >> <https://lists.opendaylight.org/mailman/listinfo/controller-dev> > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > <mailto:controller-dev@lists.opendaylight.org> > https://lists.opendaylight.org/mailman/listinfo/controller-dev > <https://lists.opendaylight.org/mailman/listinfo/controller-dev>
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
