What is discouraged when it comes to process and component management in AtomSphere?

Making copies for versioning is discouraged in AtomSphere because it can lead to confusion and an increase in inefficiency within the development and deployment process. Instead of creating multiple copies of components to maintain different versions, effective version control practices should be employed. This includes utilizing AtomSphere's built-in version management features which allow developers to track changes and revert to previous versions without the need for duplicating components.

By relying on the platform's versioning capabilities, teams can maintain a clearer and more organized project structure. This practice ensures that all team members are working with and referencing the same versions of components, which helps to enhance collaboration and reduces the risk of errors stemming from outdated or conflicting versions. Furthermore, it allows for a streamlined update process, where changes can be tested and deployed more predictively.