VirtualBox

Changes between Version 313 and Version 314 of Testbuilds


Ignore:
Timestamp:
12/01/2017 08:31:43 AM (12 days ago)
Author:
michael
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Testbuilds

    v313 v314  
    11= VirtualBox test builds = 
    22 
    3  * If you are experiencing some problem with !VirtualBox and want to find out whether it has been fixed before you file a bug report, or 
    4  * if you just want to try out the upcoming stable release to help our quality testing or 
    5  * if you need a particular fix which we would like to make to the stable branch, but not until it has had more testing 
    6 you may wish to try out a test build of the current release series.  Here we provide you with regularly updated links to recent builds.  If one of these links does not work at any time feel free to ask us to update it on [wiki:IRC] or the [wiki:Mailing_lists development mailing list].  See below for information about installing Linux packages.  '''Regularly installing test builds and using them in your day-to-day work is one of the best ways you can help us improve the !VirtualBox user experience.''' 
     3Here we provide you with regularly updated links to recent builds.  If one of these links does not work at any time feel free to ask us to update it on [wiki:IRC] or the [wiki:Mailing_lists development mailing list].  See below for information about installing Linux packages.  '''Regularly installing test builds and using them in your day-to-day work is one of the best ways you can help us improve the !VirtualBox user experience.''' 
    74 
    8 These builds are expected to be almost as stable as released versions, and we accept bug reports against them.  They may contain some features which we plan to include in a future stable release but not necessarily the next.  For any mission critical use of !VirtualBox we of course always recommend purchasing a support contract.  See the [#development_snapshots development snapshot] section below if you are more adventurous. 
     5== Stable branch builds == 
     6If you are experiencing some problem with !VirtualBox and want to find out whether it has been fixed before you file a bug report, if you want to help our quality testing, or if you just want a particular fix early, you may wish to try out a test build of the current release series. 
     7 
     8These builds are expected to be almost as stable as released versions, and we accept bug reports against them.  They may contain some features which we plan to include in a future stable release but not necessarily the next.  For any mission critical use of !VirtualBox we of course always recommend purchasing a support contract. 
     9 
     10== Development branch builds == 
     11If you make any sort of mission-critical use of !VirtualBox - particularly if you do not have a support contract - you are advised to regularly try out our development branch builds to make sure that everything you depend on still works as you expect.  Catching problems at the development stage greatly improves your chances of having them solved before they reach a stable release, and increases your voice in the development process.  The builds are usually usable for day-to-day work - we use them ourselves - for people who can deal with occasional surprises.  Please report development build problems on [wiki:IRC] or the [wiki:Mailing_lists developer mailing list], not on the bug tracker. 
    912 
    1013A list of things worth testing for in test builds can be found here: [wiki:Technical_documentation#RegressionTesting Regression Testing]. 
     
    2730= [=#development_snapshots Development snapshots] = 
    2831 
    29 For those who want to take a look at what is happening at the rough edge of !VirtualBox development, whether out of interest or to get early testing of your own particular use case between releases, we also make development snapshots available.  These are usually usable for day-to-day work - we use them ourselves - but only for people who can deal with occasional surprises.  We are always happy to be told about problems with development builds (on [wiki:IRC] or the [wiki:Mailing_lists developer mailing list], not on the bug tracker) but may not be able to do anything about them quickly.  It is probably a good idea to subscribe to the developer mailing list if you plan to test these, to avoid reporting the same problems several times and to be able to investigate them jointly with other people. 
    30  
    31 These links may not always work, as we will update them on demand.  Feel free to ask if you would like them updated. 
    32  
    3332[[Include(wikitestbuildsfile:testbuilds_trunk.html)]] 

www.oracle.com
ContactPrivacy policyTerms of Use