Appreciate the community support sorry if your quoting-reply got removed in the cleanup.
In real news we're going to publish Syscoin 0.1.5 RC1 tonight. Because we want to make sure everything is rock solid the release we publish tonight will be considered a "release candidate". What this means is - for all intensive purposes - this is the final release. Before we officially promote it to that position we want some users to get hands-on time with it.
Release Candidates will be a pattern we follow moving forward with future releases as well. This gives the community time to use the wallet and provide feedback to the team prior to that build becoming the "production wallet". We are merging some stuff in Github and will have binaries posted tonight. If no major issues or requests come up in 24-48hrs this will be promoted to a production release as-is. If items are found we will address them before promoting. Because this is a release candidate the 0.1.4c wallet will still remain the official "production wallet" pending community feedback on 0.1.5 RC1.
This strategy allows the community to provide feedback while also hardening/testing the client on a much larger scale than we are able to reproduce in our testing environments. This release doesn't introduce any changes that require a hardfork so you can use it freely on the main network and it is not restricted to testnet. In the future, if we have changes that do impact the actual network (such as assets feature, or other changes that may impact network) these will be released in "release candidate" form on the testnet first. We'll establish an official public testnet and testnet policy when we get to that point.
More coming very soon!
In real news we're going to publish Syscoin 0.1.5 RC1 tonight. Because we want to make sure everything is rock solid the release we publish tonight will be considered a "release candidate". What this means is - for all intensive purposes - this is the final release. Before we officially promote it to that position we want some users to get hands-on time with it.
Release Candidates will be a pattern we follow moving forward with future releases as well. This gives the community time to use the wallet and provide feedback to the team prior to that build becoming the "production wallet". We are merging some stuff in Github and will have binaries posted tonight. If no major issues or requests come up in 24-48hrs this will be promoted to a production release as-is. If items are found we will address them before promoting. Because this is a release candidate the 0.1.4c wallet will still remain the official "production wallet" pending community feedback on 0.1.5 RC1.
This strategy allows the community to provide feedback while also hardening/testing the client on a much larger scale than we are able to reproduce in our testing environments. This release doesn't introduce any changes that require a hardfork so you can use it freely on the main network and it is not restricted to testnet. In the future, if we have changes that do impact the actual network (such as assets feature, or other changes that may impact network) these will be released in "release candidate" form on the testnet first. We'll establish an official public testnet and testnet policy when we get to that point.
More coming very soon!
Nice approach... community involvement!
