Hi David, Team,

Sorry to be a late voice in this. If you put out release candidates, I'll
test them in a couple of use cases (basically all of the cases I use FS
for):

   - Building under Linux (I'll typically be running the latest build of
   Ubuntu).
   - Fast-rendering a collection of MIDI files and testing the result.
   - Running FS as the music back-end for DOSBox in a couple of MPU-401
   games.

That isn't much beyond the basic use cases of FS, but I don't really use it
for anything more advanced.

Do you think it would be helpful to have some kind of form (perhaps a
Google Doc spreadsheet) where we can each have ownership over a couple of
columns (for example, I would have 3 columns for the above test cases) and
manually mark off the success shortly after the release candidate is out?
Maybe we can have 7 days to run the tests after the RC is released.

Matt
_______________________________________________
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev

Reply via email to