News for Debian developers
This wiki page collects small news that all developers should know but that are not worth a dedicated mail to debian-devel-announce. Follow the template "Example of news" and add your news below it. If there are some other items already, please sort your item in descending order of importance to the Debian development community. See /Help for more information on how to write entries. If you have any questions, please ask the publicity team or the Debian English localisation mailing-list.
If you are able to post to debian-devel-announce (all Debian members can) and there are 5 or more items below, you might want to send out the news. To send out a new issue, you can use this helper script to generate the email version of this page. After generating the mail, proof-read it, correct any spelling, formatting or grammatical errors and send out the mail. Once the mail is sent and archived, please delete the items that were sent, add a link to the archived mail in the Previous news section and mention the mail in ProjectNews.
Example of news
This is a sample news. Copy it and edit the title, content and signature... You can use links like this. Put real news below this sample.
-- Your Name
lintian contributors needed
If you are interested in working on it, please join the lintian group on salsa (DD will be accepted instantly, non-DD should show some contributions first, e.g. via Merge Requests), add yourself to the lintian team wiki page, join the debian-lint-maint mailing list, and review the bugs filed against lintian, issues on salsa and merge requests on salsa (1 2).
-- Paul Wise + Axel Beckert
CPU instruction selection documentation
New documentation has been written summarising all the options for selection of CPU instructions, including porting between SIMD instructions, emulating atomic instructions, manual runtime code path selection, manual runtime function selection, compiler function multi-versioning, glibc hwcaps library selection, runtime binary selection, blocking installation and blocking running binaries. When you discover a package has limited portability due to a higher baseline, use of SIMD/atomic instructions, or other CPU instruction related problem, please consider perusing the new documentation, improving the portability using the documented techniques and contributing your changes upstream where possible. If you see others discovering these issues, please suggest they take a look at the documentation.
-- Paul Wise, Gioele Barabucci and Bastien Roucaries