Merge lp:~jtv/launchpad/bug-779701 into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 13002 |
Proposed branch: | lp:~jtv/launchpad/bug-779701 |
Merge into: | lp:launchpad |
Diff against target: |
349 lines (+137/-76) 2 files modified
lib/lp/archivepublisher/scripts/publish_ftpmaster.py (+33/-29) lib/lp/archivepublisher/tests/test_publish_ftpmaster.py (+104/-47) |
To merge this branch: | bzr merge lp:~jtv/launchpad/bug-779701 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Henning Eggers (community) | code | Approve | |
Review via email: mp+60346@code.launchpad.net |
Commit message
[r=henninge][bug=779701] Create distroseries indexes per suite.
Description of the change
The new, python-based publish-ftpmaster script will create archive indexes for a new distroseries. In the Ubuntu release process this removes a manual "publish-distro.py -A" run for the distroseries. However we want the indexes for each suite in the series created separately, with a separate publish-distro run. This will make it easier to add pockets in the future, for instance. Index creation should be tracked separately for each suite.
This branch makes the index-creation code use the suite name instead of the distroseries name for the marker files that indicate that indexes have been created. It then runs publish-distro separately for each suite.
To test:
{{{
./bin/test -vvc lp.archivepubli
}}}
To Q/A:
* Create a new distroseries for an existing distribution.
* Run cronscripts/
* See that indexes have been created.
* Note marker files in the distribution's archive root, one for each suites.
(The marker files are dot files, so may not show up by default).
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
Thank you for this nice improvement. All I have to add is this:
- Consider using a local factory method for the frozen distro series that also explains why it needs to be frozen.
- The test naming is inconsistent. You used the right convention for the new tests but left the old ones as they were. Would be nice if you could update those, too, where applicable (test_methodNam e_condition) .
Cheers,
Henning