Merge lp:~laney/launchpad/proposed-notautomatic into lp:launchpad
Status: | Work in progress |
---|---|
Proposed branch: | lp:~laney/launchpad/proposed-notautomatic |
Merge into: | lp:launchpad |
Diff against target: |
196 lines (+55/-25) 7 files modified
lib/lp/archivepublisher/publishing.py (+4/-2) lib/lp/archivepublisher/tests/test_publisher.py (+32/-16) lib/lp/registry/configure.zcml (+1/-0) lib/lp/registry/interfaces/distroseries.py (+12/-0) lib/lp/registry/model/distroseries.py (+1/-0) lib/lp/soyuz/scripts/initialize_distroseries.py (+3/-0) lib/lp/soyuz/scripts/tests/test_initialize_distroseries.py (+2/-7) |
To merge this branch: | bzr merge lp:~laney/launchpad/proposed-notautomatic |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Richard Harding (community) | Needs Information | ||
Review via email: mp+113921@code.launchpad.net |
Commit message
Add flag proposed_
Description of the change
Summary
=======
Users are offered upgrades to packages in -proposed, which is often used as a staging/test area. It would be better if they were able to opt in on a per-package basis.
Proposed Fix
============
Add a flag which causes the -proposed Eelease files for a series to contain the NotAutomatic and ButAutomaticUpgrade flags, so that users are not offered updates by apt to packages in -propoed, but are offered upgrades within it.
Test
====
bin/test -cvv test_publisher
QA/demo Plans
==============
Upload (or copy) a package into quantal-proposed with proposed_
Unmerged revisions
- 15424. By Iain Lane
-
Fix missing copy of proposed_
not_automatic when initialising new series - 15423. By Iain Lane
-
Lint and including remove some unused imports.
- 15422. By Iain Lane
-
Add DistroSeries.
proposed_ not_automatic to set NotAutomatic ButAutomaticUpg rades This means that users will not be offered upgrades to packages in -proposed for
series with this flag enabled, but will be offered upgrade within it.
One thing I don't know is whether the way that I modified the tests is the best way to go about this. In particular I'm not sure about the "set_flag" functions.
Perhaps both tests should just be combined?