Flatout

From Wine-Wiki

Jump to: navigation, search

Apparently this software is a demolition derby game that is available on the pc and other game machines.

1 Wine Application Database
2 Links

[edit] Wine Application Database

As of [Oct 08] there are entries in the application database.

http://appdb.winehq.org/objectManager.php?sClass=application&iId=2685 Main Listing Version 1. Some platinum, some gold
- http://appdb.winehq.org/objectManager.php?sClass=version&iId=3911 Version 1 rated as platinum. two maintainers.
http://appdb.winehq.org/objectManager.php?sClass=application&iId=4915 Main Listing Version 2. - this appears to be a mix up. Perhaps this should be merged with the first listing.
- http://appdb.winehq.org/objectManager.php?sClass=version&iId=7578&iTestingId=13891 Two maintainers. Needs more recent tests. Please add them if you can
- http://appdb.winehq.org/objectManager.php?sClass=version&iId=9406&iTestingId=17181 Two maintainers. Needs more recent tests. Please add them if you can.

Can you add your results to the Official Wine Appdb? Submitting your results for this software under Wine will help the many other users who run Wine.

Become a Maintainer

Have you considered volunteering to be an additional Maintainer for this software.

Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.

Who can be a Maintainer? - anyone. no programming experience required.
What is required of a Maintainer? - not much, but you do make a real difference.

Official Information

Unofficial Information

Wine_Appdb_Maintainer

A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help.

Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.

This often results in very quick fixes.

Further Help to Wine
If you are able to keep an eye out for bug reports for your software and adding a note to the bug report whether you can confirm if it is a real bug or not, you can help the bugzilla team and developers spend more time on improving Wine. For each Wine release, make a small note in the bug confirming whether it is still present or if it has been fixed.