Page History

This page describes Apache CloudStack`s components retirement process.  We would love not to retire any component, and integrate even more CloudStack with other software and systems. However, when some integration becomes broken and nobody else is using and willing to put the energy and resources required to properly maintain and develop it, then it is time to give some peace to the broken plugin. Retirement is a natural process; it is part of life! The retirement of an unused and broken component can free energy that can be directed to new and exciting features and integrations. The process occurs in two major steps, first disabling the build of the component, and later after a period of, at least, six (6) months, the retired component is removed.

...