| Summary: | Updates Release notes | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Manuel Hiebel <manuel.mageia> |
| Component: | Installer | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | release_blocker | CC: | fri |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/release-notes.html | ||
| Whiteboard: | |||
| Source RPM: | mageia-release | CVE: | |
| Status comment: | |||
|
Description
Manuel Hiebel
2021-02-20 18:39:05 CET
I removed the line on the wiki https://wiki.mageia.org/mw-en/index.php?title=Mageia_8_Release_Notes&diff=50499&oldid=50482 Assignee:
bugsquad =>
mageiatools Wiki pages I was thinking shuold wait until decided to release. After that there is about two days to announcement. That is how i plan to treat Errata page. (Update Notes section, and remove issues that are solved between RC and final) CC:
(none) =>
fri yes, but always remember release notes gets pulled in on release isos too I gutss we need some specific tagging that http://svnweb.mageia.org/packages/cauldron/mageia-release/current/SOURCES/Makefile?view=markup can trigger on and remove when syncing release-notes Ah, thats how it works, thanks. Yes, tagging fro automatic removal would be nice. Or even some substitution. Would be nice to have some mean to test run that, easily executed by us less programatic literate QA Fixed in mageia-release-8-3.mga8 Resolution:
(none) =>
FIXED (In reply to Morgan Leijström from comment #4) > Ah, thats how it works, thanks. > > Yes, tagging fro automatic removal would be nice. > Or even some substitution. > Would be nice to have some mean to test run that, easily executed by us less > programatic literate QA mgarepo co mageia-release cd mageia-release/SOURCES make update check contents of release-notes.* |