When using the package development model, which metadata changes do you need to track manually?

When using the package development model, which metadata changes do you need to track manually?

• A. Changes To Components Not Yet Supported By Source Tracking
• B. Only Changes Made Via The Setup UI
• C. All Metadata Changes For The Release
• D. None. All The Changes Are Tracked Automatically

Answer: (A)

Not all metadata is captured by source tracking in the package development model. You must manually track changes to components that aren’t yet supported by source tracking to ensure they’re included in the release and can be reproduced in other environments. Source tracking handles many types automatically, but gaps remain for certain metadata types, so manual tracking fills those gaps. Changes made only via the Setup UI aren’t the whole story, and you can’t assume every metadata change is tracked automatically since some types aren’t supported yet. Manual tracking is required specifically for those unsupported components.

Not all metadata is captured by source tracking in the package development model. You must manually track changes to components that aren’t yet supported by source tracking to ensure they’re included in the release and can be reproduced in other environments. Source tracking handles many types automatically, but gaps remain for certain metadata types, so manual tracking fills those gaps. Changes made only via the Setup UI aren’t the whole story, and you can’t assume every metadata change is tracked automatically since some types aren’t supported yet. Manual tracking is required specifically for those unsupported components.