By installing the Beta version of our software farmerswife (fw), you hereby confirm that you understand and agree to the consequences thereof as listed below:
For customers who have purchased feature development, it is a prerequisite to run the Beta version within their production environment.
Without purchased feature development the access to Beta is only granted on a case-per-case basis at our own discretion.
Any prior issues (bugs, missing functionality, etc.) or new ones related to the upgrade to the Beta version need to be addressed separately and conform to the below bug report format. Being on Beta doesn't mean that all issues can or will be addressed; some might require unplanned and purchased feature development.
You hereby authorize us to include your Company Name, City, and Country to the list of Beta Customers within the Beta Release Notification email. All recipients you have informed us about (see below list), will receive this notification once a next Beta version is ready to be downloaded and installed. All recipients are added as "BCC".
We need to know the First Name, Last Name, Title, email address of:
- Main Farmer(s)
- Main IT contact(s)
- Main farmerswife user(s)
You also confirm:
All users who work with your farmerswife system running on "Beta" were previously informed about the following information.
You agree to upgrade as soon as possible, once we've notified you about a new release.
The Release Notes are available online and are updated with every release notification and shipped with each installer, these are the first and only line of documentation during the Beta development phase. The content is essential for everyone running a farmerswife Beta version. You agree to read them and distribute them among your users.
New feature development bears the higher risk of new bugs being introduced, or previously working functionality to contain bugs. We need to be able to replicate the bugs, in order to fix them. The issues you might encounter will not go away by magic. We need your help here: report bugs to support@farmerswife.com. Use the below format, which it makes it easier for us to clearly understand the issue:
Bug or issue report:
Email Subject: a clear and short description of the problem or bug. For example: "farmerswife Client crash on opening Project #12345 on WIFE-Beta-version-xyz" is already a lot more useful than "farmerswife crashes" or "problem".
Email content:
DO:
WHAT and WHERE is the issue?:
Describe in simple words and as detailed as needed in the shortest possible way :) on how to replicate the issue. Any window in farmerswife has its own title name. Using these descriptions is the best and easiest way to communicate to us, to what you are referring too within the system.
Please also consider adding screen shots and please make sure all needed information is visible on it. When trouble shooting issues, surrounding info on the screen shots typically helps us a lot. We will instantly see, if you're working on Mac or Windows, we can see the date and time when this happened and it helps us to see, where in farmerswife the issue is happening.
HAPPENS:
Describe in simple words what happened after the above actions.
SHOULD:
Describe what you expected to happen.
If a farmerswife Client app crash was involved, we need the "error.txt" from the machine where the crash happened; the error.txt is located in the installation folder of the farmerswife Client software.
Please see below where to find the file.
Windows Path
The path to find the error.txt on Windows is the local farmerswife Client root installation folder where this crash happened; for example C:\Program Files\Farmers WIFE\
Mac Path
To find the error.txt on Mac OS X "Ctrl + click" on the farmerswife Client application icon and select "Show Package Contents" from the pop-up menu.