Closed xoebus closed 5 years ago
Before I merge this, we should discuss what the plan for informing folks about this organization change. Any concourse resources will need to be updated and the cloudfoundry-incubator
release will no longer be updated. Thoughts?
Are there any consumers that wouldn't be kept working by the redirect?
The redirect only works for github. The bosh-io releases will be under the new organization, and the old organization will stop being updated.
OIC. I figured folks were using the GitHub releases resource instead.
Generally we just send an email to the correct mailing list and make the switch.
Maybe a redirect feature on bosh.io would also be useful?
Probably something we are unlikely to prioritize. We can have both organizations in the index for a while if we want to allow a transition.
Let's just make the switch and cause the resources to fail. I'm going to send an email out about BPM 1.1 at some point soon. I'll include a note about this in that and then we can merge this and flip the switch.
Sounds good.
The
bpm-release
repository was recently moved fromcloudfoundry-incubator
tocloudfoundry
. This change updates the release index to point at the new location.