Andrew Benson

First off, I would like to thank everyone for their enthusiasm and interest in giving Max 5 a test drive. This release comes at the end of a very intense and productive beta-testing phase, and a great deal of work has gone into making it as flawless as possible. However, it is inevitable that there will be a couple of little issues that have slipped by even our most observant testers. Over the next several weeks, the Cycling '74 team will be working hard to process and resolve any bugs that you all spot along the way. 

In order for us to best serve this goal, we would like to ask that all bug reports include as much useful information as possible. Please see the bug reporting guidelines below for a general outline of what we expect in a complete bug report.

As always, installation issues and authorization problems can be sent directly to support at cycling74 dot com.

+++++++++++++++++++++++++++++++++++++++++++++++++++

Please report any problems you experience with clear and complete

information, including steps to reproduce, software and system

information, and where possible, an isolated example patch and crash

log. Something like the following would be ideal. This makes it

easier for us to find and fix the problems you experience. Without

such clear and complete information, it is less likely we will be

Provide a descriptive summary of the issue.

In numbered format, detail the exact steps taken to produce the bug.

Describe what you expected to happen when you executed the steps above.

Please explain what actually occurred when steps above are executed.

Describe circumstances where the problem occurs or does not occur,

such as software versions and/or hardware configurations.

Provide additional information, such as references to related

problems, workarounds and relevant attachments.

First off, I would like to thank everyone for their enthusiasm and interest in giving Max 5 a test drive.  This release comes at the end of a very intense and productive beta-testing phase, and a great deal of work has gone into making it as flawless as possible.  However, it is inevitable that there will be a couple of little issues that have slipped by even our most observant testers.  Over the next several weeks, the Cycling '74 team will be working hard to process and resolve any bugs that you all spot along the way. 
In order for us to best serve this goal, we would like to ask that all bug reports include as much useful information as possible.  Please see the bug reporting guidelines below for a general outline of what we expect in a complete bug report.

Please report any problems you experience with clear and complete
information, including steps to reproduce, software and system
information, and where possible, an isolated example patch and crash
log. Something like the following would be ideal. This makes it
easier for us to find and fix the problems you experience. Without
such clear and complete information, it is less likely we will be
able to.

Summary:
Provide a descriptive summary of the issue.

Steps to Reproduce:
In numbered format, detail the exact steps taken to produce the bug.

Expected Results:
Describe what you expected to happen when you executed the steps above.

Actual Results:
Please explain what actually occurred when steps above are executed.

Regression:
Describe circumstances where the problem occurs or does not occur,
such as software versions and/or hardware configurations.

Notes:
Provide additional information, such as references to related
problems, workarounds and relevant attachments.


Max 5 Bug Reporting