Bug 9516

>This has been mentioned in the pastebin since a long time but nothing is done.
pastebin ? 

but indeed I can confirm.

Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakxtools

Sorry, I meant parinux pad

*** Bug 9839 has been marked as a duplicate of this bug. ***

CC: (none) => mageia

Is this an easy fix?

Setting release blocker with minor severity as it can't be fixed after release.

Priority: Normal => release_blocker
CC: (none) => eeeemail, mageia
Severity: normal => minor

not really a blocker I think

I agree. It was MrsB who judged it to be so.

Only in so far as it can't be rectified after release with an update. 
That was the agreed use for release_blocker tag. Severity _IS_ set to minor..

Only in so far as it can't be rectified after release with an update. 
in diskdrake it could with an updates, for in the network installer too (if it's updated but was never the case)

in diskdrake it could with an updates, for in the network installer too (if it's updated but was never the case)


In all the ISOs we actually QA test and publish then, it couldn't be.
That to me at least seems to fit the definition. 

I may have misunderstood.

Well, AFAIK it's not a regression, it's been that way all the time. I would say we decrease it and maybe we can fix it for Mageia 4.

WDYT?

CC: (none) => sander.lepik

I wasn't expecting it to be fixed for Mageia 3, just applying the correct tags for the bug.

I'll stop doing so I think and leave them to you guys to sort out.

Release blocker is a bug that stops us from releasing :)

Anyway, decreasing priority.

Priority: release_blocker => Normal

Release blocker was previously agreed to be a bug which could not be fixed with an update after release. Priority and Severity are two different things and no one alone gives a true impression of the overall importance of a bug.

There seems to be some confusion/inconsistency about the use of release_blocker tag though so it's something we should discuss after release and work out a better system if needs be.

The decision whether to release or not is taken by humans with an overview of all the bugs, not just when the list of bugs which just happen to have their priority set != release_blocker reaches zero.

set TO release_blocker* even

(In reply to claire robinson from comment #13)
> Release blocker was previously agreed to be a bug which could not be fixed
> with an update after release.

I can't remember such agreement :/ English is not my maiden language but "release blocker" itself is a pretty straightforward status. We wouldn't have saved search for release blocker bugs and we wouldn't discuss them during dev meetings so often if those bugs don't stop us from releasing the next version of Mageia :)

For bugs in installer we have special component in bugzilla and you can be pretty sure that if the bug is filed under that component it can't be fixed after release ;) But it's another matter if it's blocking release or not :)

If you look at the release critical bugs then you can see that many of them are not in installer and could be fixed with update but many of them would also ruin the first impression, so we have to fix them before release.

Yep. It's been used inconsistently. It was initially agreed to be used in the way I said though. 

We'll need to look at this after release to see if there is a better way to use it, probably in the way you're saying. It makes the most sense that way after all. If so we should maybe introduce another priority setting for bugs which can't be fixed after release to allow for more flexibility in the use of the actual release_blocker tag. Or perhaps use a release_blocker Keyword instead.

In either case though this particular bug obvious shouldn't 'block' the release :)

This bug is still present in "Mageia 4 alpha2 Boot Nonfree 64bit CD ISO".

Created attachment 4360 [details]
Image screen shot: Mageia installer screenshot partitioner text cropped.

setting severity back to normal (it had been set to minor to compensate for the release blocker setting, which has been reverted)

(In reply to PC LX from comment #17)
> This bug is still present in "Mageia 4 alpha2 Boot Nonfree 64bit CD ISO".

s/4alpha1/4alpha2/ on the whiteboard

CC: (none) => marja11
Whiteboard: 4alpha1 => 4alpha2
Severity: minor => normal

Valid for 4alpha3

Whiteboard: 4alpha2 => 4alpha3

Valid for 4beta1

Whiteboard: 4alpha3 => 4beta1

Fixed in 3rd prerelease round of M4beta2

So:

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

uh? There has been no specific fix...

Then it is caused by the screen being off centre more than usual left aligned :))

IOW an accidental fix.