Remove in-memory-channel ClusterChannelProvisioner in 0.7

[Harwayne]

The in-memory-channel ClusterChannelProvisioner provides a synchronous Channel, which we no longer want. in-memory is an equivalent async Channel. in-memory-channel should be removed after everyone has had the chance to migrate off of it.

Additional Info

#708 created the in-memory ClusterChannelProvisioner. It will be included in the 0.4 release. We should wait one complete release before removing in-memory-channel.

[akashrv]

Is there a way to mark anything as deprecated? Is there a deprecation followed by removal policy that Knative follows?

[akashrv]

/kind feature-request

[evankanderson]

We can add a Severity: Warning condition indicating the the objects will be removed. On the other hand, we've also supported in-memory-channel for at least one releases overlapping the new in-memory Provisioner, so I think we could evict this for 0.5.0 or 0.6.0.

[matzew]

generally like this, @evankanderson have some "deprecation" warning, and kill it with 🔥 afterwards

[sebgoa]

This needs to be clearly stated in the release-notes with a DEPRECATION warning.

[Harwayne]

#1062 added a deprecation condition. That will go out in 0.6.0, so it is safe to remove in 0.7.0.

[Harwayne]

/assign

[akashrv]

/milestone v0.7.0