BETA program for Dwarfguard 2.0 is starting
The development of the next major of Dwarfguard - version 2.0 - has come to the phase when all the biggest architectural changes are done and working and we work on primarily customer-requested features and some yet-to-be-implemented minor features and improvements.
This is an ideal time to start the BETA program as it allows the customers requesting the features to verify the implementation brings the requested functionality.
As with the Dwarfguard 1.0 BETA program, the Dwarfguard 2.0 BETA program has several important qualities and aspects:
- The BETA allows for incremental upgrades throughout the whole BETA, with planned upgrade step from the last BETA release to the full Dwarfguard 2.0 production release. That said, being a BETA, some of the upgrade hops may require a set of manual upgrade instructions, meaning the upgrade experience may not be as smooth as the production version upgrades.
- While being a BETA program, we still follow a release process, providing not only upgrade steps but also testing and a limited support (free of charge).
- The BETA is open to all partners and through them to all interested customers.
What is different from the earlier 1.0 BETA program is that the following version numbering will be used:
- Dwarfguard 1.1.0 will be BETA1 for Dwarfguard 2.0
- Dwarfguard 1.2.0 will be BETA2 for Dwarfguard 2.0
- and so on for as long as we will publish BETA releases
- Dwarfguard 1.9.0 will be RC1 for Dwarfguard 2.0
- Dwarfguard 1.9.1 will be RC2 for Dwarfguard 2.0
- and so on as long as needed until the production 2.0 is released
Please note that while the BETA experience is usually quite smooth with Dwarfguard and some or our customers are actually quite happy having a production deployment running on a BETA version, it is something we cannot recommend and must disregard, as BETA is still miles from a production release, especially in the terms of stability, amount of testing, and quite big functionality differences between the individual BETA releases. Also, you cannot count with receiving the same amount and quality of support for a BETA version in contrast to the production release.
Upgrade information: no upgrade path is provided as we absolutely cannot support "upgrade" from production deployment to a BETA deployment.