Update po_translatable_pages for Tails 3.0
On each release
n of Tails 3.0, 4.0, etc.
po_translatable_pages should be
updated to disable translations of
security/Numerous_security_holes_in_* for release
Also create a ticket for Tails 4.0.
Merge remote-tracking branch 'origin/feature/11573-update-po_translatable_pages' into feature/stretch
#4 Updated by intrigeri over 2 years ago
- Assignee changed from intrigeri to sajolida
- % Done changed from 0 to 50
- QA Check changed from Ready for QA to Info Needed
Looks good, merged into feature/stretch. Now, one question remains: how do we coordinate that with applying the same change on our production website? I'd rather not have this change entangled with the 3.0 release process, so how about we apply the same changes on master and have the boum.org sysadmins do the same in a coordinated way soon, without waiting for the actual release? I mean, dropping these translations when 3.0 is out is somewhat arbitrary, and I see no reason why we couldn't do it a little bit earlier. If you agree with this plan, please provide a branch based on master and I'll handle the coordination of its review+merge with email@example.com.