farmerswife Beta Agreement - cloud

Modified on Wed, 28 Jan at 11:28 AM

Using farmerswife Beta versions

By using the farmerswife (fw) Beta version, please acknowledge the points below.

Access to the Beta

If you’ve purchased feature development, running the Beta in your test and subsequent production environment is required.
Without purchased feature development, Beta access is granted case by case, at our discretion.

What to expect

Existing issues or new ones related to the Beta upgrade must be reported separately
For quick processing the should follow the bug report format below.
Being on Beta doesn’t guarantee that all issues will be fixed. Some may require additional (planned or unplanned) feature development.
All users working in your farmerswife Beta system must be informed that they are using a Beta version.
You agree to get upgraded to a new Beta release when appropriate.

Documentation

Release Notes are updated with every Beta release.
During the Beta phase, Release Notes are the primary (and only) documentation.
Please read them and share them with your users.

Contacts

Please send us the email addresses of all users that should be notified when a new Beta version is available.

Reporting Bugs

New features come with higher risk: new bugs may appear, or existing functionality may break. To help us fix issues quickly, please report bugs as soon as possible to support@farmerswife.com, using preferably the format below.

Email subject

Short and specific.
Example: “Client crash when opening Project #12345 on WIFE-Beta-xyz”
(This is much more helpful than “farmerswife crashes”.)

Email body

WHAT & WHERE

Describe the steps that led to the issue.
Use the exact window names shown in farmerswife when possible.
Add screenshots or a screen recording if you can. Make sure key details are visible (OS, date/time, and where in farmerswife the issue happens).

HAPPENS

What actually happened?

SHOULD

What did you expect to happen?