Thanks for the update John! Maybe a 'roadmap revised' update could go in the Announcements thread on the main forum when you guys make significant changes to it?
The release of the whole marketplace is shifted due to the encountered bugs with the alias implementation into the sendtoaddress command.
This needs to be fixed before.
Yes, another delay is not so good, but a buggy release is worse. The actual bugs were unexpected and took / takes our programmers more time than planned to fix it.
Hey Guys!
I've been getting married the last 2 days so apologies for the lack of replies on my end but that doesn't mean the rest of the team hasn't been here hard at work. The issue that held up 0.1.5 RC3 looks like it may be remedied and we're testing it today and will be providing a more detailed status update shortly.
I noticed there were some questions around the roadmap changes and I wanted to provide a bit more info- this will also be provided in more depth via a blog post. After discovering the issues that held up RC3 and reviewing the fact that the Release Candidate Program was not on the roadmap I shifted many of the dates to represent a more realistic timeline for developing, testing, and delivering via Release Candidate Program the upcoming releases. I didn't move any of the promotional efforts as for now there is no change there. Also we expect to deliver a number of "developer toolbox" items ahead of the official roadmap items but those are aimed toward a different yet equally important demographic when in comes to widespread adoption of Syscoin.
In addition to shifting some of the dates
additional features were added to the roadmap and some of the further-out dates were marked as *tentative*. This means the date expressed in the roadmap is the target and we're going to try to deliver on that date if nothing else changes (or sooner!). I want to remind people that
Syscoin is trailblazing a path very few other coins are- many are talkin about it, we are doing it. Because of this its easy to say lets just line up release after release but in reality we're going to be rolling out a disruptive features, getting feedback, and really pushing to get them used in mainstream applications. So for that reason
1) we want to make these releases solid, robust, and timed in a way that allows for delivery as such; and
2) if we release something like Marketplaces and a big player like Amazon comes along and wants to pilot things with us or work with us in ANY capacity- we WILL shift other roadmap items to pursue that opportunity if need be based on dev-assets. As noted at the bottom of the roadmap is it a living document and will be updated regularly. Updates will be accompanied by a blog post explaining the changes especially when it comes to major updates- I apologize for not posting this update before taking off the last 2 days, certainly an exception to my normal posting practices.
I'll post to the blog in more detail about all this and the exact changes to the roadmap and why they were made (focusing on the next upcoming releases)- but in the interim I just wanted to update people here since I've been out the last 2 days. These changes are about making the software better, while still getting community feedback, and concurrently allowing the community to know when to expect "final releases" even with the new Release Candidate period that will precede each release.