On Wed, Sep 7, 2016 at 4:08 AM, Frank Mehnert <[email protected]> wrote:
> Another reason for not explicitly mentioning changes/fixes in test builds > is > that we don't want to discourage a user from installing these builds > OK, that's one way to look at it. I guess that happens too. I won't argue (much ;). Yet on the other hand, I suggested a user to try a test build and his answer was "how do I know if it addresses any sound issues? or would my install be wasted effort?" or words to that effect. Moral of the story (the way I see it): some users are too reluctant (lazy?) and need some reasuring + encouragement to try test builds. Maybe that is something which can be worked on the test builds wiki page, some words of encouragement like "if you're currently having problems with VBox or have found a bug and don t want to wait for the next VBox update, you can download test builds from this page to run the latest code our developers are working on. These builds represent the latest code we're testing. A TEST BUILD MIGHT SOLVE your issue.(+2 font, red color) ;-)" Just thinking aloud. FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto Revolucionario - George Orwell
------------------------------------------------------------------------------
_______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
