[ kvm-Bugs-2964912 ] Web page wrong at /page/Vista_Net...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bugs item #2964912, was opened at 2010-03-07 01:44
Message generated for change (Comment added) made by jessorensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2964912&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Jakob Bohm (jbohmdk)
Assigned to: Nobody/Anonymous (nobody)
Summary: Web page wrong at /page/Vista_Net...

Initial Comment:
The page http://www.linux-kvm.org/page/Vista_Networking_Workaround currently contains two pieces of wrong (or at least misguided) information:

Currently, the full text of that page is simply:

"This issue is now resolved and Vista works with the rtl8139 driver since CVS February and newer."

1. The page says that something changed in "February", but it does not say which *year*, there is a huge difference between something changing in February 2010 or February 2008.

2. Just because some problem is solved in the CVS version of kvm (or *any* other software), it doesn't mean the change has made it to the actual real world copy of the software people are using, so any workaround, warning or other practical information for "old" bugs needs to stay available until you can be certain that the fix has been propagated all the way to all end users with regularly updated software.  For a widely distributed project such as kvm, this means that all of the following must have happened: The change has made it into the "stable" release tarballs.  These changed tarballs have been packaged by all distribution that previously packaged older affected releases.  Those distributions have included the changed packages in released distributions or upgrades for all affected past distributions.  Each distribution vendor has ended support for distribution versions containing only non-upgraded packages.  At least 12 month have passed after this became true of all distributions that included the software versions affected by the issue.  Yes, that is a very long time, but the only thing that needs to be done during that period is to keep the old contents available with a clear indication as to which tarballs included the problem and which tarballs included the fix, stating a CVS version or tag would be nice-to-have supplemental information but of little use for most people.


----------------------------------------------------------------------

>Comment By: Jes Sorensen (jessorensen)
Date: 2010-11-26 12:17

Message:
Wiki updated to say Feb 2009 given that is most likely the date based on
the wiki history of the page.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2964912&group_id=180599
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux