On 08/15/2013 09:40 AM, Paul Wouters wrote:
I feel that people mostly say "fedora is for testing". It is somewhat
supported by responses to upgrade problems to a new version which
invariable are along the lines of "we don't support that upgrade
path/method".
Well whomever choose to decide that we "support" upgrades in the first
place bypassed the QA community entirely in making that decision as well
as to which tool is "preferred","supported" or "recommended".
The fact is we have always had more testing with yum upgrade vs
preupgrade/fedup since that is always been the preferred choice of our
QA community members and what we recommend ourselves to use [1].
The bottom line is that we cannot "support" upgrades et all since we
cant test cover all the upgrade path of mixed match combination of our
ca 12.000 components. ( and that's excluding any testing with 3rd party
repo's involved ) .
We don't even provide a fallback method encase something goes awry but
hopefully that will change for all the spins that decide to default to
btrfs if/when that time comes and we should be able to implement
something that boots into the volume before upgrade.
From my personal opinion we should not be "supporting" upgrade et all
since in all reality we cant do that and we end up sending misleading
signals to Fedora consumers when doing that.
JBG
1.
https://fedoraproject.org/wiki/Releases/Rawhide?rd=Rawhide#Yum_from_Existing_install
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
