It is sad to see how Broadcom cannot do padding right for mobile…

But on topic: why not create docker.io/bsi and let /bitnami as is without new updates? Then nothing breaks; it just won’t be possible to do upgrades. You’ll then figure out why and possibly seamlessly switch to your own build or BSI.

▲

david_allison 5 days ago | parent | next [-]

> But on topic: why not create docker.io/bsi and let /bitnami as is without new updates?

If people are relying on you for automatic security updates, and you've decided to no longer provide these updates [for free], users should opt in to accept the risk.

This would normally require user action (after a period of warnings/information), and having the fix look 'obviously' unsafe (`/bitnami ` ->`/bitnamilegacy`) feels reasonable.

▲

orthoxerox 5 days ago | parent | prev | next [-]

Because "bitnami" has brand value. It makes business sense to reuse the name for the new service you are trying to sell.

	▲	Aeolun 5 days ago \| parent [-]
		Any brand value that bitnami has will be entirely destroyed by this incomprehensible change. People will associate the ‘bitnami’ namespace with “can’t possible utilize for long term production use”

▲

cube00 5 days ago | parent | prev [-]

> It is sad to see how Broadcom cannot do padding right for mobile…

It's on brand when you consider how badly the styling in Rally needs an update.