Changes

Line 69: Line 69:  
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''
 
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''
   −
Sugar loosely depends on the ds-backup-client RPM package, maintained by OLPC and XSCE in two ds-backup repositories.  Changes to this dependent package are required by this feature.  Coordination with ds-backup developers will be required, to avoid combining incompatible versions of Sugar and ds-backup.  SoaS systems won't be affected because they do not have ds-backup.
+
Sugar loosely depends on the ds-backup-client RPM package, maintained by OLPC and XSCE in two ds-backup repositories.  Changes to this dependent package are required by this feature.  Coordination with ds-backup developers will be required, to avoid combining incompatible versions of Sugar and ds-backup.
 +
 
 +
OLPC OS and derivatives will be affected, and coordination with their developers required.  SoaS, Fedora and Ubuntu systems won't be affected because they do not have ds-backup.
    
== Contingency Plan ==
 
== Contingency Plan ==