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

[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 CelsoProvidelo:
https://launchpad.canonical.com/Soyuz/NativeSourceSyncing

The comment on the change is:
checkpoint, it's still incomplet

------------------------------------------------------------------------------
  
  == Summary ==
  
- This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. Mention tables being created.
+ The so called 'Native Source Sync' procedure will reduce the time spent by maintainers making possible to instantly copy or move source and binary publications across suites or even distributions.
  
  == Rationale ==
  
- This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.
+ While helping to reduce duplicated information stored in the SourcePackageRelease table when dealing with multiple distribution, Native Source Sync will also promote quick and sane basis for "real world" derivation.
  
  == Use cases ==
  
@@ -21, +21 @@

  
  == Assumptions ==
  
-  * "Moving NascentUpload business logic to DistroReleaseQueue* content classes" (cprov: do we need a spec for that)
+  * NascentUpload code cleanup (nascentupload-cataclysm)
  
  == Design ==
  
+ Based on the use-cases above we highlight the following design requirements:
+ 
-  * Tool to sync a source and/or its binaries from one distrorelease/pocket to another
+  * Tool to sync a source and/or its binaries from one suite (distrorelease/pocket) to another;
+  * Target sources/binaries will be assumed as trusted code and won't be verified again.
+  * Each sync should contain a 'changesfile' with proper changelog.
+  * Synced binaries will preserve the original build information.
-  * The sync will be materialized as a new/accepted DRQ entry and inherit features like:
+  * The sync will be materialized as a NEW/ACCEPTED DistroReleaseQueue entry and inherit features like:
     * pre-publication manual override,
     * auto override,
-    * pending approval workflow for new items.
+    * pending approval workflow for NEW items.
-    * etc
   * Commandline syntax: {{{packagesync debian/unstable/foo/1.0-1 ubuntu/edgy}}}
- 
  
  == Implementation ==
  
- This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
+ Not yet.
  
  === UI Changes  ===