All the news that fits, we print.
This is the 341 issue of the Wine Weekly News publication. Its main goal is to bring that warm fuzzy feeling that you get when you look at a baby puppy with those big, beady eyes to all it's readers. It also serves to inform you of what's going on around Wine. Wine is an open source implementation of the Windows API on top of X and Unix. Think of it as a Windows compatibility layer. Wine does not require Microsoft Windows, as it is a completely alternative implementation consisting of 100% Microsoft-free code, but it can optionally use native system DLLs if they are available. You can find more info at www.winehq.org
|
This week, 662 posts consumed 972 K. There were 124 different contributors. 75 (60%) posted more than once. 37 (29%) posted last week too. The top 5 posters of the week were:
|
| News: Wine Versions 0.9.54 - 0.9.56 | Archive | |
|---|---|---|
|
Wine
Wine 0.9.54, Wine 0.9.55 and Wine 0.9.56 have been released since the last issue of WWN:
Wine 0.9.54 was released today, with the following main changes:
* Photoshop CS/CS2 should now work, please help us testing it.
* A number of RPC fixes.
* Various improvements to the debugger support.
* Lots of bug fixes.
Wine 0.9.55 was released today, with the following main changes:
* Direct3D improvements, including driver version emulation.
* Beginnings of support for OLE objects in Richedit.
* Several fixes to the animation control.
* A bunch of fixes for regression test failures.
* Lots of bug fixes.
Wine 0.9.56 was released today, with the following main changes:
* Proper handling of OpenGL/Direct3D windows with menu bars.
* Stubs for all the d3dx9_xx dlls.
* Several graphics optimizations.
* Many installer fixes.
* Improved MIME message support.
* Lots of bug fixes.
WWN has been delayed these past few weeks for several reasons, hopefully all of which have been cleared up and WWNs should flow once a week. There may be some lapses where there's only one issue for a period of two weeks, but I will do my best to be weekly. Also, I've heard that some people have not found my weekly 'purpose of this weeks WWN' exciting enough (in the opening summary). I'll do my best to kick those up a notch :). Important: the AppDB stats at the end of this issue take into account the entire month since the last WWN, hence their (huge) size. The Bugzilla stats also are since the last issue. | ||
| Google comes out of the closet! | Archive | |
|---|---|---|
|
Supporting Wine
As you may know by now, Google supports the development of Wine by contributing patches. They do this not only because they love being the big, squishy, teddy bear of open source love, but also because it helps them run applications like Picasa cross platform. Dan Kegel summarizes Google's support for wine in the year 2007: Google uses Wine primarily as the basis for the Linux port of our photo management software, Picasa. [...] CodeWeavers did the initial port, and Googlers Lei Zhang, Nigel Liang, and Michael Moss are improving Wine further for Picasa 2.7. Beyond Picasa, a few of us (Lei Zhang, Alex Balut, and I) have been fixing random Wine bugs in our 20% time. I've also been doing regular Valgrind runs over the Wine test suite, pestering developers who accidentally check in code that Valgrind doesn't like. Google also sponsored some work by CodeWeavers to improve support for Photoshop ('cause so many people want it) and for Dragon Naturally Speaking ('cause even Linux users get RSI). While not yet perfect, those apps are a lot more usable now as a result. In particular, Photoshop CS and CS2 are quite usable indeed. (See https://wiki.winehq.org/AdobePhotoshop for details.) I also had the pleasure of hosting eight students as Google interns working on Wine throughout the year. Here are their names, and roughly what they worked on: Dan Hipschman: widl Evan Stade: gdiplus, Powerpoint Viewer James Hawkins: msi Jennifer Lai: win16 conformance tests Juan Lang: crypt32, iTunes Matt Jones: mono testing Mikolaj Zalewski: Photoshop, Limux Roy Shea: svchost, BITS So, you're wondering, what exactly does that all boil down to? I tallied all our accepted patches recently; the list is now up (along with the exact Wine source we use for Picasa) at http://code.google.com/opensource/wine.html I was pleasantly surprised at the size of the list. Separately, Google also sponsored nine Summer of Code students this year. Just to name two who remain active even after the end of summer: Alex Sørnes, who improved Wine's Wordpad, and Maarten Lankhorst, who solved tons of sound problems. (And oh, how nice it is to not have to change sound settings anymore!) All that may sound like a lot, and perhaps it is, but it pales compared to the work put in on Wine by the rest of the Wine developers. Thanks, everybody! I'm really looking forward to Wine 1.0 (which, according to Alexandre, is planned for sometime in 2008). Dan Kegel Software Engineer Google Interestingly, there are 1905 patches in that list which spans a period of about 2 years. If we assume there are 250 business days a year, that's 500 business days. That results in about 4 patches a day, or a patch every 2 hours! This post has also been sited elsewhere at Ars Technica and apcmag.com (Credit for the witty title of this article also goes to Dan Kegel) | ||
| War on 'make test' | Archive | |
|---|---|---|
|
Tests
A lot of developments have been made on the war against test failures on Wine. The current status is visible here . Dan Kegel pushed the big red button back in the beginning of February to initiate the series of patches to begin fixing all test suite failures: Great progress was made at WineConf last year on getting our test suite closer to always passing on wine, but http://test.winehq.org/data/200801301937/#Wine shows that, according to the results collected from people who run programs/winetest on Wine, twelve DLLs' tests are currently failing. (Let alone the test failures on Windows!) http://bugs.winehq.org/show_bug.cgi?id=9916 also talks about the fact that "make test" shows failures. This situation greatly confuses new developers, who assume that any test failure is somehow their fault. And that's a reasonable assumption, let's make it so! It would make validating a new Wine development environment easy -- it'd be great to be able to say If it doesn't pass "make test" with no errors, something's wrong with the build environment. What's the best way to encourage people to fix these problems? Should we designate some upcoming day, week, or month as a conformance test bug squishing party? Should we offer prizes (or at least notoriety) for the person who does the best job fixing conformance test suite bugs (as judged by Alexandre or his designate)? Or is a simple call to arms enough? Jeremy White went back and attempted to build his own winetest executable and export his results. Apparently winetest was not well documented, and Jeremy had a bit of trouble: Okay, so I boldly tried to use winetest with what documentation I could find, and had an...um...interesting time. ... It ran, did it's thing, and had one interactive thing (Gecko fussed at me; that's not a Winetest bug afaik). Then when it was all done, it transferred my nearly 1 MB file, and then errored out with: "Unknown build id" So then I looked at the output file, and sure enough, it had a - for build info, not my fancy git id. So I hacked that, put in jwtip, and then ran winetest -s to send my output file through. And then I have a lovely result here: http://test.winehq.org/data/jwtip/ So that's *something* at least. Although I suspect someone will now have to go clean up my mess :-/. Cheers, Jeremy Reece Dunn also had some experience with winetest:
The easiest thing I found for generating test results on Wine is to
treat it like Windows. That is, download the
winetest-[buildid]-paul-mingw.exe from the build you want to test and
run:
Maarten Lankhorst also is seeming to have some good results:
Hi all,
As of this publication there are still a couple (countable on your fingers) number of tests failing on wine. The most recent tests I can find are at http://test.winehq.org/data/wine-0.9.55-279-g456a94b/ | ||
| Lots of Stub d3dx9_* dll stubs | Archive | |
|---|---|---|
|
WineD3D
Tony Wasserka has begun implementing the following directx dlls and passing along the function calls to higher level dlls (dedx9_36):
d3dx9_24 d3dx9_25 d3dx9_26 d3dx9_27 d3dx9_28 d3dx9_29 d3dx9_30 d3dx9_31 d3dx9_32 d3dx9_33 d3dx9_34 d3dx9_35 Additionally, some interesting stats about the d3d3x*_** dlls were posted to wine-devel by Luis C. Busquets Perez. (Note: These stats were from before Tony Wasserka's big list of new beginning implementations.
Find attached some data on d3dx8, d3dx9_xx and d3dx10_xx implementations: dll files by d3dx extension: d3dx8 1 dll files d3dx9_xx 13 dll files d3dx10_xx 4 dll files Functions included in each d3dx: DLL Number of functions d3dx8 153 d3dx9_24 320 d3dx9_25 323 d3dx9_26 327 d3dx9_27 327 d3dx9_28 332 d3dx9_29 332 d3dx9_30 332 d3dx9_31 329 d3dx9_32 334 d3dx9_33 334 d3dx9_34 334 d3dx9_35 334 d3dx9_36 336 d3dx10_33 177 d3dx10_34 177 d3dx10_35 180 d3dx10_36 180 Total functions for all d3dx implementations: 5162 functions. Total functions for all d3dx implementations taking into account repetitions: 425 functions From these 425 functions: Functions specific to d3dx8: 15 Functions specific to d3dx9: 165 Functions specific to d3dx10: 71 Functions shared between d3dx8 and d3dx9: 65 Functions shared between d3dx9 and d3dx10: 35 Functions shared between the three implementations: 74 On the other hand, considering individual dlls, 17 functions are only mentioned in one dll 3 functions are mentioned in 2 dlls 68 functions are mentioned in 4 dlls 2 functions are mentioned in 7 dlls 10 functions are mentioned in 9 dlls 5 functions are mentioned in 11 dlls 3 functions are mentioned in 12 dlls 149 functions are mentioned in 13 dlls 65 functions are mentioned in 14 dlls 29 functions are mentioned in 17 dlls 74 functions are mentioned in 18 dlls | ||
| Status of a Wine Forums | Archive | |
|---|---|---|
|
Wine Forums
The age old topic of how to best maintain communication between a community of developers and the community of users using their product has been brought up again recently. The key question this time is "should there be an official Wine forum?" Of course, there are many pros and cons, some people love forums, some hate them, and of course the issue that there already exists a fairly active Wine-users mailing list. In coming up with a solution, the Wine team wanted to minimize the confusion of having too many different non-centralized and disjoint sources of help. There already is the Ubuntu Wine forum, independent Wine forums, IRC, and the mailing list, so adding another official channel for communication seemed like the wrong thing to do. In steps Jeremy Newman with an idea. Jeremy set up a new phpBB on winehq.org which is linked directly to the wine-users mailing list. This results in the best of both worlds: helping those who really like forums and those who really like mailing lists, while keeping both essentially the same source of information. The only issue is that phpBB, in all its ubiquity, has become a large target for spammers. Within hours the forum and the users-list were under siege. After a long weekend of fighting and implementing new techniques, Jeremy Newman has hopefully come out on top. Yeah, it has been difficult. Since I've never run a PHPbb board before, I never know how well these bots had the registration system down. It has really raised my blood pressure a bit this weekend. I think I've come up with a solution that will work for everybody. First, I updated the "captcha" image validation to be more random and harder to screen scrape. Second, I added a text validation field that asks you: "Who is the current maintainer of the Wine project?" This should stop both bots and human spammers that don't know about our forum. To be nice, I at least added a hint link, that takes you to the "About Wine" page on WineHQ, so new users will at least have to read a little bit of our history if they don't know. | ||
| Work on ITunes? | Archive | |
|---|---|---|
|
iTunes
Dan Kegel stirred up a bit of a hornets nest mentioning the "next big apps" to tackle (covered below) and including iTunes in his potential list. Christopher Harvey: What needs to get done for iTunes to work? James Hawkins: 80% of bug fixing development is figuring out the answer to that question. If we knew all that was needed, it wouldn't take that long to fix. Maarten Lankhorst: v7.6 basically works if you set windows version to windows vista, and find out why the installer fails to create the 'Bonjour service' registry stuff properly. I submitted 8 or so stub dll's to wine-patches that make iTunes v7.6 actually start after installation. It checks for the dll's and silently fails if they don't exist. I haven't done any further testing yet though, but it looks like it is probably a small installer bug that prevents itunes v7.6 from installing without first manually creating those registry keys. So iTunes needs a (lot) of work to be up and running fully. However, the point was brought up that for a lot of iTunes functionality, there exists viable Linux-native alternatives. iTunes would, however, provide syncing etc. which for many would be very useful. Overall, it was decided that the discussion of whether or not it's "worth it" to work on an application because of alternatives is pretty moot. | ||
| Next Big Apps to Tackle | Archive | |
|---|---|---|
|
Wine
Dan Kegel: Now that Adobe Photoshop CS2 is running kind of well (there are bugs that need fixing, but I'm trying to look ahead a bit), what big app(s) are worth focusing on next? Using https://wiki.winehq.org/LinuxApplicatonRequestSurvey, skipping Photoshop (which we should continue to fix up) and the ones that are either too hard, have native versions, or are probably something CodeWeavers might already be doing, and adding in good old Framemaker (so close to working we might want to go for it just for the goodwill from all those tech writers), I think that leaves about seven big ticket apps, in rough order of popularity:
https://wiki.winehq.org/AdobeDreamweaver
I've created wiki pages with trial download URLs for all but iTunes, and done a bunch of triage on them. Most of these could all use more triage and bugs filed. At some point the dust might settle, and it might become clearer which one(s) deserve to be focused on. I think Maarten is going to try iTunes, which would be great. - Dan And the list of applications begins to flow. L. Rahyen: What about support for Autodesk products (such as AutoCAD and 3ds max)? As far as I know there is two group of problems preventing them from working: copy-protection related and .NET related. This is true for most recent versions. However for not-so-new versions there is no .NET issues (just copy-protection problems). For example this is true for 3ds max 4, 5, 6, 7 (but I didn't check this personally). I heard that it is possible to get 3ds max 3 working on WINE but it's so old that this is useless today but it gives hope that newer versions of 3ds max will work if proper support for copy-protection used by Autodesk will be implemented. This is true for AutoCAD too (as far as I know AutoCAD and 3ds max are using same protection called C-Dilla). Unfortunately, I'm not an expert on this topic so I don't know how difficult to implement proper support for C-Dilla. But if it's implemented, it is very likely that both AutoCAD and 3ds max will work (as I said, because of .NET issues, most recent versions may not work but at least not so new versions will work; in future, when .NET support will be better, new versions will probably work too). In other words, proper support for C-Dilla is most important thing for AutoCAD and 3ds max support so it is possible to temporary ignore .NET bugs related to most recent Autodesk products for now. By the way, AutoCAD and 3ds max are very popular applications. It's easy to check how they are popular by using Google. For example, for AutoCAD alone you will get 43,800,000 results [1]. So there is a really a lot of people who depends on Autodesk products such as AutoCAD. And Dan Kegel's response (which is a good conclusion for the issue as a whole): Yeah, getting .net working would be great, and we seem to be making some progress there. And getting the copy protection used by these apps would be great. Googling around, I see that C-Dilla has sometimes been called Safecast, which is related to Safedisc, so I took the liberty of updating https://wiki.winehq.org/SafeDisc with a link to the Autocad 2000 bug, http://bugs.winehq.org/show_bug.cgi?id=8466 . That one looks like it's waiting for some action - James pointed out a simple-looking problem, but nobody's tackled it yet. I'm torn between tackling hard problems and just going for the low-hanging fruit. I think the upshot is: I'm going to push hard on the low-hanging fruit, and let the hard problems sort themselves out in their own time, since pushing on them usually tends to involve a lot of wheel spinning. - Dan | ||
| WineHQ.org troubles | Archive | |
|---|---|---|
|
WineHQ
WineHQ has been down a bit recently and some users have begun to take notice. Jeremy White explains: The server has been getting locked up lately. Jeremy Newman thinks it's related to MySQL, as he's seen it running amok in conjunction with the crashes; he fears that recent changes to the appdb code may have triggered this, but that's mostly speculation. At this point, there is little hard data; there haven't been console or other obvious log messages that would point at a source of the problem. We do now have a mysql log file, perhaps that will shed some light. It's definitely increasing in frequency, though, as it's happened both days this weekend. Jeremy Newman: WineHQ.org, AppDB, and Bugzilla are all on the same server. We have been having some issues with mysqld crashing the entire server. It so far has been a hard issue to track down. I've been tweaking the mysql config settings to hopefully prevent this issue. And later, another letter from Jeremy Newman: As many of you have noticed we've been having a bit of server trauma this past month. The issue boils down to a bug somewhere in mysqld. We are still trying to find the exact cause of the bug. We do have some leads. I just wanted to do a brain dump on wine-devel here before I go on Vacation for a week. The problem: mysqld will randomly eat up all resources on the system until the server is completely unresponsive to anything but pings. My band-aids thus far: 1. mysql is now running at a nice of 1. This should allow us to at least ssh in and kill it if it gets out of control again. 2. I've removed InnoDB table support to save on memory. Not many tables where using it anyway, and nothing is using transaction support at this time. 3. I've patched the appdb to use memcached for session management. This will reduce some load on the DB as the session table was busiest and slowest table of the appdb. These fixes should give longer uptime, but they are not solving the core issue. While I'm gone, if the server goes offline again, please contact Alexandre or Jeremy White. They can kick proverbial butt of the server to get it going again. Lastly, sorry for the issues. -Newman Follow-up: A few days ago Jeremy Newman disabled a feature called "fuzzy search" on the AppDB which, thus far, has been the magic cure we've been looking for and reliability has gone way back up! | ||
| Wine 1.0 status update | Archive | |
|---|---|---|
|
Wine 1.0
Dan Kegel writes in with a progress report on Wine 1.0: We now have about 100 bugs nominated for fixing in 1.0. Thanks to everybody who nominated bugs. Now it's time to winnow the list a bit. 1.0 bugs should be 'important' somehow, easy to reproduce, and have some chance of actually being fixed by, say, summer. The better understood a bug is, the more likely it is it can be fixed for 1.0, so even less important bugs can be 1.0 bugs if they're well enough understood and a patch is available. Here are a few bugs I'm thinking of deferring, and why: Not important enough http://bugs.winehq.org/show_bug.cgi?id=5807 Mercora IMRadio crashes http://bugs.winehq.org/show_bug.cgi?id=6048 Stokes crashes http://bugs.winehq.org/show_bug.cgi?id=8687 everestpoker and Programmer's Editor don't work http://bugs.winehq.org/show_bug.cgi?id=9288 Armed Assault doesn't load web page http://bugs.winehq.org/show_bug.cgi?id=9895 Alzip crashes Probably not doable by summer http://bugs.winehq.org/show_bug.cgi?id=609 Add BiDi support Not well enough understood: http://bugs.winehq.org/show_bug.cgi?id=6383 Dual-core not being correctly supported Do people agree with those assessments, and are there other bugs nominated for 1.0 that don't quite deserve it? - Dan | ||
| Weekly AppDB/BugZilla Status Changes | Archive | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
AppDB / BugZilla
*Temporary Disclaimer: For the better part of the month of January Wine's bugzilla will be going through an annual triage and cleanup. While the following statistics are still meaningful, (perhaps even moreso than otherwise) they are very skewed from normal Wine BugZilla activity.
*Disclaimer: These lists of changes are automatically generated by information entered into the AppDB. These results are subject to the opinions of the users submitting application reviews. The Wine community does not guarantee that even though an application may be upgraded to 'Gold' or 'Platinum' in this list, that you will have the same experience and would provide a similar rating.
Updates by App Maintainers
Updates by the Public
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
All Kernel Cousin issues and summaries are copyright their original authors, and distributed
under the terms of the
GNU General Public License,
version 2.0.
