[Launchpad Wiki] Update of "Soyuz/NativeSourceSyncing" by Julianedwards

[Launchpad Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Launchpad Wiki" for change notification.

The following page has been changed by Julianedwards:
https://launchpad.canonical.com/Soyuz/NativeSourceSyncing

The comment on the change is:
Some tweaks based on IRC with Celso

------------------------------------------------------------------------------
  == Rationale ==
  
  While helping to reduce duplicated information stored in the SourcePackageRelease table when dealing with multiple distribution, Native Source Sync will also promote a quick and sane basis for "real world" derivation.
+ 
+ For example, an updated package lives in the 'proposed' pocket until it is considered ready for release, at which point its version is incremented and it has to be re-uploaded to go to the 'updates' pocket.  This is problematic because:
+  * It creates duplicated source and binary package release files
+  * The version has to change and the code is rebuilt which can introduce bugs
  
  == Use cases ==
  
@@ -41, +45 @@

  
  == Implementation ==
  
+ The implementation will be staged as follows:
+  1. copy between pockets (PROPOSED -> UPDATES, SECURITY -> UPDATES, no rebuild, i.e, include binaries)
+  1. copy between distrorelases (feisty-RELEASE -> edgy-BACKPORTS, rebuild, do not include binaries, replace backport-source.py)
+  1. copy between distribution (debian-unstable -> ubuntu.feisty-RELEASE, rebuild, do not include binaries, replace sync-source.py)
+ 
  Based on design requirements above we can highlight the following implementation details:
  
   * DistroReleaseQueue creation should not require a changesfiles.
-  * We will land an enhanced pre-publication override layer (required for debian syncs)
+  * We will land an enhanced pre-publication override layer (required for debian syncs).  This will override component/section/priority when copying packages.
   * Source syncs can optionally carry their binary.
-  * Synced binaries will preserve the original build information.
+  * Synced binaries will preserve the original build information of distro/release/pocket/architecture.
   * Reference entities will be verified for sanity during Queue.accept()
     * Claimed sources files match found SourcePackageRelease,
     * Claimed SourcePackageRelease matches claimed BinaryPackageRelease,