From Fedora Project Wiki

  • ...monbugs for issues that should be copied to F20'' - this was done, and F19 commonbugs cleaned up a bit * cmurf was working on a mail to anaconda list proposing a restriction on the breadth of custom partitioning coverage
    60 KB (7,830 words) - 06:57, 30 December 2013
  • ...a media or ISO images methods to workaround this issue. Note that neither Anaconda not Preupgrade verified the authenticity of the source either and this is n ...([[PreUpgrade]] and DVD) that have been used in previous Fedora releases. Anaconda, the Fedora installer does have not any in-built upgrade functionality in F
    15 KB (2,443 words) - 14:40, 23 January 2013
  • # jlaska and adamw discussed documenting the outstanding bugs requesting CommonBugs documentation. The process is detailed at https://fedoraproject.org/wiki/C | style="color: #407a40" | adamw: I started documenting the installer related CommonBugs ... I should have the remaining installer issues knocked out shortly. If y
    35 KB (4,361 words) - 17:26, 7 March 2011
  • == Fedora 17 pre-planning: anaconda GUI rewrite == * Anaconda team has a complete rewrite of the GUI pending and tentatively planned to l
    66 KB (8,797 words) - 02:46, 16 November 2011
  • * Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:
    45 KB (7,201 words) - 00:00, 15 March 2018
  • * adamw to talk to anaconda devs and get a build done for beta tc1 with live keyboard bug fixed ...one: https://fedoraproject.org/wiki/Common_F20_bugs . Do add or mark with 'CommonBugs' keyword any other bugs you think ought to be listed
    48 KB (6,149 words) - 00:30, 1 October 2013
  • | style="color: #407a40" | did we get the new anaconda and NM in RC1? | style="color: #488888" | dennis says the new anaconda was in there
    58 KB (6,982 words) - 19:27, 11 August 2011
  • | style="color: #407a40" | that doesn't quite tie in with anaconda views it, but then i don't think we're quite at the point where GNOME gets | style="color: #407a40" | if you install GNOME and don't create a user in anaconda, yes.
    59 KB (7,383 words) - 05:50, 5 July 2013
  • #* pungi is going to inherit splittree and pkgorder from anaconda-runtime; need to integrate the functionality of those into pungi code ...<td class="text" style="color: #8c4a4a">I'm still collecting stuff for the CommonBugs page</td><td class="time">13:26</td></tr>
    36 KB (6,047 words) - 16:40, 13 February 2015
  • * anaconda » master * ACTION: several remaining CommonBugs? needing documentation(jlaska, 01:25:15)
    41 KB (5,854 words) - 18:46, 8 March 2010
  • ...iki/Common_F16_bugs will need entries for the bugs on http://bit.ly/fedora-commonbugs-proposed # j_dulaney - check in with anaconda and releng teams on the feasibility of making the rats point (08-31) an ear
    44 KB (5,540 words) - 15:06, 29 August 2011
  • ...144" | so the obvious action item that we need to get done today is to get commonbugs up | style="color: #818144" | roshi: have you worked on commonbugs at all yet?
    58 KB (7,284 words) - 10:16, 25 September 2013
  • ...r: #488888" | jreznik: define top issues - the list that adamw started in #anaconda? | style="color: #488888" | #topic (892621) Anaconda FC18-TC4 does not present BIOS RAID as available storage
    121 KB (15,166 words) - 02:53, 31 January 2013
  • | style="color: #818144" | i've pretty much done commonbugs ...bugs that should be called out there...do add them or tag the bug with the commonbugs keyword
    31 KB (3,789 words) - 09:04, 18 September 2016
  • * Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:
    50 KB (7,917 words) - 23:59, 14 March 2018
  • : Identify and document '''CommonBugs?''' issues (see [[Common_F14_bugs#My_bug_is_not_listed|process]]) ...only outstanding items on the QA plate that I'm aware of for F-14-Beta are CommonBugs?
    47 KB (6,030 words) - 09:03, 18 September 2016
  • * Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:
    51 KB (8,078 words) - 23:59, 14 March 2018
  • | style="color: #488888" | #info Proposed Blocker, anaconda, VERIFIED | style="color: #407a40" | it's already fixed anyway, and anaconda 18.28 is pending stable
    48 KB (5,690 words) - 04:11, 1 February 2013
  • ...be great if everyone could ensure that their 'favourite' alpha bug has the CommonBugs keyword, i tried to mark the biggest ones as we went along but i may have m | style="color: #4b904b" | tflink, adamw: actually for anaconda, fesco required in ticket status report week before beta change deadline
    51 KB (6,412 words) - 23:56, 21 September 2012
  • ...hat before F-15-Alpha is released, we need to document the current list of CommonBugs -- [[Common_F15_bugs]] | style="color: #488888" | given that we didn't change anaconda, i would expect rc2 to wind up good.
    65 KB (8,197 words) - 09:03, 18 September 2016
View ( | ) (20 | 50 | 100 | 250 | 500)