This is a NOOP release since there was an issue with our release scripts

Visit: https://github.com/knative/eventing/releases/tag/knative-v1.7.1

Eventing

• Created a new in-memory Channel which buffers events and decouples
  sender and receiver. The previous in-memory-channel implementation
  was blocking and senders would block until the event had been
  delivered to the destination. (Thanks to @sbezverk)
• Add NATS ClusterChannelProvisioner. (Thanks to @radufa)
• Separated several ClusterChannelProvisioners from the core. (Thanks to @matzew)
• Add a Knative-message-history attribute recording the channels
  traversed by the event
  (https://github.com/knative/eventing/pull/688)
• Several eventing resources (ClusterChannelProvisioner, Subscription,
  in-memory, GCP PubSub channels) now emit corev1.Events to improve
  debugging (https://github.com/knative/eventing/pull/746).
• Cleanup of Conditions to hide Severity=Error when conditions are
  ready.
• Improved cleanup of subscription and reply.
• Fixes to ensure Istio injection in the knative-eventing namespace.

Eventing Sources

• Updated CloudEvents library to better handle both v0.1 and v0.2.

Upgrade notes

• Knative Eventing now requires Kubernetes 1.11, and provides the
  /status subresource. This causes metadata.generation to behave
  like other Kubernetes objects.
• All conditions in Source statuses now have a Severity field
  indicating if the condition is terminal or non-terminal. See
  https://github.com/knative/serving/issues/2394#issuecomment-436806801.

Eventing core

• Channels now create VirtualServices using generateName, which should
  prevent collisions with similarly-named objects from other types
  (such as Knative Services).
• Subscriptions now work with Knative 0.1 and 0.2.0 Services.
• Defined and documented the ability to select a default
  ClusterChannelProvisioner if one is not specified by the Channel.
• The legacy pre-0.2 routing resources have been removed.

In-memory channel

• No substantial changes.

Kafka channel

• Improved cleanup of finalizers to prevent Kafka channels from
  remaining stuck forever if provisioning fails.

Upgrade notes

• On upgrade from 0.2.0 there will be <10 seconds of unavailability for all in-memory channels. During this time all messages sent to in-memory channels will be lost. The in-memory channel has no durability or reliability guarantees and should only be used for testing or ephemeral messaging.

Eventing core

• Subscriptions may only subscribe to Channels in the same namespace.
• Subscriptions can be deleted after their subscribed Channel is deleted.
• Channels without a specified provisioner will have a default provisioner applied. The default provisioner is specified in the knative-eventing/default-channel-webhook ConfigMap and defaults to in-memory-channel.
• The ClusterChannelProvisioner is now part of the provisioner CRD category.

In-memory channel

• In-memory channel is now the default for Channels that don't specify a provisioner.
• Renamed channel dispatcher k8s service from in-memory-channel-clusterbus.svc.cluster.local to in-memory-channel-dispatcher.svc.cluster.local.

Kafka channel

Initial release.

First Knative Eventing alpha release!