REAPER pre-release builds

schwa · 06-29-2008, 07:24 PM

The latest pre-release build can be found here.

Pre-release discussion should only happen here.

If you come across a bug, please report it along with a recipe to reproduce. Feedback on new features under development is always welcome.

Added for emphasis: Prerelease software should be expected to have bugs. The purpose of a public alpha/beta/RC process is to help identify bugs in a real-world context. Prerelease builds will contain experiments, tests, and lots of new code.

You can install the prerelease just like a regular update, overwriting the release version, or you may prefer to install to a separate location on disk, or even do a portable installation. As with any update, you can always re-install the latest release version over the prerelease at any time.

Justin · 12-17-2016, 08:10 AM

As a followup, here are some thoughts on on preferred etiquette for posting in the prerelease threads:

Feature requests: please do not post general feature requests in the pre-release forum. If you have a suggestion DIRECTLY related to the behavior and/or scope of a new feature of the build in question, it is generally polite to post and discuss there.

Bug reports: please test against the last public release to make sure the bug represents a regression from the public release! If the public release is affected by this bug, post in the bug reports forum (or reply to the relevant thread if you find it). Regressions from previous pre-releases are also helpful. Please include in the post any information on the versions you tested (so we can narrow down when the issue was created).

Taking the effort to test the previous public release (and possibly pre-releases) is immensely helpful for us and will improve our throughput.

06-29-2008, 07:24 PM	#1
schwa Administrator Join Date: Mar 2007 Location: NY Posts: 16,572	REAPER pre-release builds The latest pre-release build can be found here. Pre-release discussion should only happen here. If you come across a bug, please report it along with a recipe to reproduce. Feedback on new features under development is always welcome. Added for emphasis: Prerelease software should be expected to have bugs. The purpose of a public alpha/beta/RC process is to help identify bugs in a real-world context. Prerelease builds will contain experiments, tests, and lots of new code. You can install the prerelease just like a regular update, overwriting the release version, or you may prefer to install to a separate location on disk, or even do a portable installation. As with any update, you can always re-install the latest release version over the prerelease at any time. Last edited by schwa; 12-17-2024 at 06:47 AM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

12-17-2016, 08:10 AM	#2
Justin Administrator Join Date: Jan 2005 Location: NYC Posts: 16,130	As a followup, here are some thoughts on on preferred etiquette for posting in the prerelease threads: Feature requests: please do not post general feature requests in the pre-release forum. If you have a suggestion DIRECTLY related to the behavior and/or scope of a new feature of the build in question, it is generally polite to post and discuss there. Bug reports: please test against the last public release to make sure the bug represents a regression from the public release! If the public release is affected by this bug, post in the bug reports forum (or reply to the relevant thread if you find it). Regressions from previous pre-releases are also helpful. Please include in the post any information on the versions you tested (so we can narrow down when the issue was created). Taking the effort to test the previous public release (and possibly pre-releases) is immensely helpful for us and will improve our throughput.