All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of Kodi is done, the suite to upload these new Kodi packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no release critical bugs exist for the Kodi package in the Debian Bug Tracking System, the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.

NOTE that if any release critical bugs are found in the version of Kodi that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.

For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.

Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.

There are times where bugs need to be fixed for versions of Kodi packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the Urgency field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.