Bug 15983 - Release notes contain notice - Page is still being written ..etc
Summary: Release notes contain notice - Page is still being written ..etc
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14069
  Show dependency treegraph
 
Reported: 2015-05-19 16:50 CEST by claire robinson
Modified: 2015-05-22 15:42 CEST (History)
5 users (show)

See Also:
Source RPM: mageia-release
CVE:
Status comment:


Attachments

Description claire robinson 2015-05-19 16:50:06 CEST
Release notes still contain the notice that the page is still being written. This will need to be removed before the final ISO build so the release notes are generated cleanly.


Reproducible: 

Steps to Reproduce:
claire robinson 2015-05-19 16:51:18 CEST

Priority: Normal => release_blocker
CC: (none) => ennael1, tmb
Hardware: i586 => All
Blocks: (none) => 14069
Assignee: bugsquad => doc-bugs

Comment 1 Marja Van Waes 2015-05-20 09:09:02 CEST
(In reply to claire robinson from comment #0)
> Release notes still contain the notice that the page is still being written.
> This will need to be removed before the final ISO build so the release notes
> are generated cleanly.
> 

I assume that can only be done just before the very last time mageia-release is built for final 5 release?

docteam members do generally not have the right to touch mageia-release, unless they have package commit rights, so reassigning to the default assignee.

However, docteam can remove those lines from the wiki, when told final release is about to happen.

Assignee: doc-bugs => bugsquad
CC: (none) => doc-bugs, marja11
Source RPM: (none) => mageia-release

Comment 2 Florian Hubold 2015-05-20 09:13:24 CEST
Quickly glanced over the links, and all seem to be current. The important ones, like for the download page are ok, so why not remove the notice? At some point the wiki page needs to be snapshotted for the release, it's probably inevitable to edit it later on if any issues might arise.

Only added one link to the actual UEFI guide in https://wiki.mageia.org/en/Mageia_5_Release_Notes#UEFI 

One old link is in there: http://doc.mageia.org/installer/4/en/content/selectInstallClass.html
But from what I understood from doc team, the complete documentation will not be completed before release, no?

Are there are any major parts missing?
Comment 3 Rémi Verschelde 2015-05-20 09:14:55 CEST
We don't need to keep the draft template for this page a few days before the final release.
Comment 4 Marja Van Waes 2015-05-20 09:37:45 CEST
(In reply to Florian Hubold from comment #2)

> 
> One old link is in there:
> http://doc.mageia.org/installer/4/en/content/selectInstallClass.html
> But from what I understood from doc team, the complete documentation will
> not be completed before release, no?
> 

We'll only know when mageia 5 is released which exact changes will (still) be in it. 

However, atelier did already add a Mageia 5 version of the manuals on doc.mageia.org
Comment 5 Marja Van Waes 2015-05-20 09:42:23 CEST
(In reply to Florian Hubold from comment #2)

> 
> Only added one link to the actual UEFI guide in
> https://wiki.mageia.org/en/Mageia_5_Release_Notes#UEFI 

Thx

> Are there are any major parts missing?

UEFI
Comment 6 claire robinson 2015-05-20 09:44:50 CEST
Just needs the template removed, when you think it's appropriate to do so. Before the last iso build though obviously so that it is included without the template.

There are a couple of translation links at the top too but they are less obtrusive than the template when the page is taken out of context like that.
Comment 7 Anne Nicolas 2015-05-20 21:18:46 CEST
Removed mention to dev release as we are now very near from final one.
Comment 8 Anne Nicolas 2015-05-22 15:42:49 CEST
mageia-release 5.0.13

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


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