Bug 10175 - Some links on the Mageia french home page are still pointing to Mageia 2
Summary: Some links on the Mageia french home page are still pointing to Mageia 2
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: www.mageia.org (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Atelier Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-20 14:07 CEST by Stéphane Couturier
Modified: 2013-05-20 17:07 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Stéphane Couturier 2013-05-20 14:07:37 CEST
I noticed that some links on the french Mageia home page (http://www.mageia.org/fr/) are still pointing to Mageia 2 wiki pages when the download link is pointing to Mageia 3.

Could someone please correct the links of "Notes de publication" (release notes) and "errata" to point to Mageai 3 pages?.

The pages are:
https://wiki.mageia.org/en/Mageia_3_:_Notes_de_Version_-_FR
and
https://wiki.mageia.org/en/Mageia_3_Errata_Fr

Thanks.
Comment 1 Manuel Hiebel 2013-05-20 14:16:48 CEST
fixed thanks, iirc, they are not yet completely updated from the english version, feel free to help

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 2 Philippe Didier 2013-05-20 14:36:45 CEST
Not truely fixed :
The links lead to the english pages :
https://wiki.mageia.org/en/Mageia_3_Release_Notes
instead of
https://wiki.mageia.org/en/Mageia_3_:_Notes_de_Version_-_FR

https://wiki.mageia.org/en/Mageia_3_Errata
instead of
https://wiki.mageia.org/en/Mageia_3_Errata_Fr

Status: RESOLVED => REOPENED
CC: (none) => philippedidier
Resolution: FIXED => (none)

Comment 3 Manuel Hiebel 2013-05-20 14:42:01 CEST
oups I break english string should be ok

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Comment 4 Stéphane Couturier 2013-05-20 17:07:29 CEST
merci :)

re "feel free to help" => the french errata page is now fully updated based on the english one ;)

Note You need to log in before you can comment on or make changes to this bug.