Add archival options
Bug #987100 reported by
Jeff Breidenbach
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Postorius |
Fix Released
|
High
|
Florian Fuchs |
Bug Description
Expose mailmans archival booleans as a tristate, either none/private/public or none/local/cloud.
Related branches
lp:~flo-fuchs/postorius/archival_options
- Terri: Approve
-
Diff: 20706 lines (+3943/-16289)24 files modifiedsrc/postorius/forms.py (+16/-2)
src/postorius/static/postorius/css/style.css (+9/-0)
src/postorius/templates/postorius/base.html (+1/-1)
src/postorius/templates/postorius/domain_index.html (+0/-2)
src/postorius/templates/postorius/lists/archival_options.html (+23/-0)
src/postorius/templates/postorius/menu/list_nav.html (+3/-0)
src/postorius/tests/fixtures/vcr_cassettes/archival_options.yaml (+144/-0)
src/postorius/tests/fixtures/vcr_cassettes/list_members_access.yaml (+647/-4070)
src/postorius/tests/fixtures/vcr_cassettes/list_members_page.yaml (+373/-1822)
src/postorius/tests/fixtures/vcr_cassettes/test_list_archival_options.yaml (+390/-0)
src/postorius/tests/fixtures/vcr_cassettes/test_list_archival_options_disable_archiver.yaml (+89/-0)
src/postorius/tests/fixtures/vcr_cassettes/test_list_archival_options_enable_archiver.yaml (+121/-0)
src/postorius/tests/fixtures/vcr_cassettes/test_list_creation.yaml (+267/-1734)
src/postorius/tests/fixtures/vcr_cassettes/test_list_index.yaml (+263/-1361)
src/postorius/tests/fixtures/vcr_cassettes/test_list_members_add_moderator.yaml (+244/-1254)
src/postorius/tests/fixtures/vcr_cassettes/test_list_members_add_owner.yaml (+244/-1254)
src/postorius/tests/fixtures/vcr_cassettes/test_list_members_add_owner_new_owner_added.yaml (+9/-94)
src/postorius/tests/fixtures/vcr_cassettes/test_list_members_new_moderator_added.yaml (+9/-94)
src/postorius/tests/fixtures/vcr_cassettes/test_list_metrics.yaml (+403/-2465)
src/postorius/tests/fixtures/vcr_cassettes/test_list_summary.yaml (+418/-2128)
src/postorius/tests/mailman_api_tests/__init__.py (+15/-0)
src/postorius/tests/mailman_api_tests/test_archival_options.py (+168/-0)
src/postorius/urls.py (+3/-0)
src/postorius/views/list.py (+84/-8)
tags: | added: mailman3 |
Changed in postorius: | |
status: | New → Confirmed |
tags: | added: mailman3-suite-blocker |
Changed in postorius: | |
assignee: | nobody → Yash (yashmehrotra95) |
Changed in postorius: | |
status: | Confirmed → In Progress |
Changed in postorius: | |
milestone: | none → 1.0.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
"none/private/ public" is an access control policy selector. It does need to be exposed.
"none/local/cloud" is more of a designation of the archive location.
Since there is more "configuration" associated with the archive access, I don't think that this is a useful distinction.
Also, one server might be archiving various lists to a number of different locations.
And, do we allow for one list to be archived in more than one place at the same time?