On Thu, Mar 21, 2013 at 5:21 PM, Animesh Chaturvedi <animesh.chaturv...@citrix.com> wrote: > >> >> > > >> >> > > I am checking if these can be reassigned. If it does not pan out >> >> > > by >> >> tomorrow I will propose to disable the feature for 4.1 release. >> >> > >> >> > I think that a decision is predicated on a more specific statement >> >> > of what we mean by "disable". >> >> >> >> Pinging on this again. I'm leaning towards agreement, but what >> >> *exactly* can we do to disable it and (at the same time) minimize the >> >> knock- on effect of the change required to disable it. >> > [Animesh>] There is no one available to pick up these defects in time for >> 4.1 so we will disable the feature. Disable means Baremetal will be removed >> from componentContext.xml , the API and UI will not be available. >> >> Are you sure that removing the plugin from componentContext.xml will >> remove it from the UI? (I'm not, that's why I'm asking) > [Animesh>] Yes, discussed with Alex and Jessica.
Link?
