First of all, thanks to Scott for the thorough look at Versions and all the feedback coming forth from it, as well as to everyone who commented here for the criticism and inspiring discussion.
I probably wouldn't be posting this if that were all I wanted to say, since it sounds like the default thing that comes out of a company who's product is being (p)reviewed. I'm writing this in response to the comment Josh Bryant posted just a little while ago. (not quoted here, since it's probably right above this one)
I think I understand where Josh is coming from; updates for Disco have been scarce and I understand how that can annoy people who didn't see the bugs they reported being taken care of for too long.
On behalf of our entire team I'd like to say: sorry, we will do our utmost best to do better in the future. I hope that the 1.0.3 update to Disco, released February 28th, serves as an indication of our desire to improve (and most of all, as a means to seeing those bugs get fixed).
To balance Josh's criticism, I'd also like to point to the updates we have shipped for Checkout, our other product. These provide the most concrete proof we have that we do release updates, do care about our products, and most of all, do care about the people who choose to use our software.
Below is a list of links to the release notes for each significant Checkout update that shipped since Checkout 1.0 was made available for sale in December 2006. The dates of each update can be found in comments in the html source of their respective release notes.
All of these releases �including version 2.0� have been made available as free updates for every Checkout user.
The above list of updates doesn't change anything, but I hope that it will help provide a more balanced and complete picture to those who want to judge us by our track record.
If anyone wants to discuss this topic further, please feel free to email me at my first name at madebysofa.com.
by Dirk Stoop — Jun 03
First of all, thanks to Scott for the thorough look at Versions and all the feedback coming forth from it, as well as to everyone who commented here for the criticism and inspiring discussion.
I probably wouldn't be posting this if that were all I wanted to say, since it sounds like the default thing that comes out of a company who's product is being (p)reviewed. I'm writing this in response to the comment Josh Bryant posted just a little while ago. (not quoted here, since it's probably right above this one)
I think I understand where Josh is coming from; updates for Disco have been scarce and I understand how that can annoy people who didn't see the bugs they reported being taken care of for too long.
On behalf of our entire team I'd like to say: sorry, we will do our utmost best to do better in the future. I hope that the 1.0.3 update to Disco, released February 28th, serves as an indication of our desire to improve (and most of all, as a means to seeing those bugs get fixed).
To balance Josh's criticism, I'd also like to point to the updates we have shipped for Checkout, our other product. These provide the most concrete proof we have that we do release updates, do care about our products, and most of all, do care about the people who choose to use our software.
Below is a list of links to the release notes for each significant Checkout update that shipped since Checkout 1.0 was made available for sale in December 2006. The dates of each update can be found in comments in the html source of their respective release notes.
Checkout 1:
1.0, 1.0.1, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.2
Checkout 2:
2.0, 2.0.1, 2.0.2, 2.1, 2.1++.
All of these releases �including version 2.0� have been made available as free updates for every Checkout user.
The above list of updates doesn't change anything, but I hope that it will help provide a more balanced and complete picture to those who want to judge us by our track record.
If anyone wants to discuss this topic further, please feel free to email me at my first name at madebysofa.com.
Thanks,
Dirk