Question Exclude forums
- Thread starter Hybr!d
- Start date
- Status
So we shouldn't get paid for past work because a few of our customers believe it's missing a feature?
If we stopped charging, we'd never be able to update it at all, ever. We -can- update it, and we -will-, in the future.
When you paid for the product, you paid for the features that were in place at the time of purchase.
If we stopped charging, we'd never be able to update it at all, ever. We -can- update it, and we -will-, in the future.
When you paid for the product, you paid for the features that were in place at the time of purchase.
Yeah, but I don't believe we promised a set number of updates or a set number of features within that time period.
The 3 month licence is for those who feel that the Pro version of the product does what they need, and they can expect one or two updates in that period with stability / performance / bug fixes / features they may or may not need in that period.
The 1 year licence is for those who feel that the Pro version of the product does what they need, and also look forward to receiving at least one major version update (v1.x -> v2.0) with new and improved functionality.
The Lifetime licence is for those who feel that the Pro version of the product does what they need, and also want to receive all product updates that will be released, ever.
I'm not 100% sure I'm doing a good enough job of explaining this, but try looking at it like this:
Say you purchased a 3 month licence of vBActivity, and immediately expect vBActivity to be the only product updated in the next 3 months (or until it does everything you want it to do.)
Then, someone else purchases a 3 month licence for vBShop.
Are they not entitled to the same treatment for vBShop as you are for vBActivity?
If yes, then to make this possible, we need one coder per product. This would, in turn, mean that the total paycheck of each coder goes down as a result. This again would mean that DBTech would not sustain that coder like a normal job would, and as such they would not be working for DBTech.
For this reason, we rotate each product so that they all receive the same amount of Major (v1 -> v2), Feature (v1.1 -> v1.2) and Maintenance (v1.1.1 -> v1.1.2) updates more or less the same number of times per year.
We also work on new products, and implement them into the cycle, because we're constantly requested to make new products.
That being said, I do believe vBActivity is scheduled to receive a code update that will enable it to work with the new Advanced Post Thanks / Like v1.1 (currently in Beta stage for Pro customers) in the not too distant future, and depending on the amount of time I have I will try to fit this feature in that update for you
The 3 month licence is for those who feel that the Pro version of the product does what they need, and they can expect one or two updates in that period with stability / performance / bug fixes / features they may or may not need in that period.
The 1 year licence is for those who feel that the Pro version of the product does what they need, and also look forward to receiving at least one major version update (v1.x -> v2.0) with new and improved functionality.
The Lifetime licence is for those who feel that the Pro version of the product does what they need, and also want to receive all product updates that will be released, ever.
I'm not 100% sure I'm doing a good enough job of explaining this, but try looking at it like this:
Say you purchased a 3 month licence of vBActivity, and immediately expect vBActivity to be the only product updated in the next 3 months (or until it does everything you want it to do.)
Then, someone else purchases a 3 month licence for vBShop.
Are they not entitled to the same treatment for vBShop as you are for vBActivity?
If yes, then to make this possible, we need one coder per product. This would, in turn, mean that the total paycheck of each coder goes down as a result. This again would mean that DBTech would not sustain that coder like a normal job would, and as such they would not be working for DBTech.
For this reason, we rotate each product so that they all receive the same amount of Major (v1 -> v2), Feature (v1.1 -> v1.2) and Maintenance (v1.1.1 -> v1.1.2) updates more or less the same number of times per year.
We also work on new products, and implement them into the cycle, because we're constantly requested to make new products.
That being said, I do believe vBActivity is scheduled to receive a code update that will enable it to work with the new Advanced Post Thanks / Like v1.1 (currently in Beta stage for Pro customers) in the not too distant future, and depending on the amount of time I have I will try to fit this feature in that update for you
galerio
Customer
Interested to see this implemented as well. It'd be nice to give awards for x amount of posts in certain forums as well.
I'd like this option too. It would be very usefull if you have new empty section and you want to encourage users to post in it by saying that in this way they gain more points!
- Status
Similar threads
- Locked
- Support ticket
- Tags
- addon admincp advanced post thanks advanced post thanks/like button buttons choose chrome comment display document documentation download firefox folder forum forums functionality html install installation internet explorer issue link manage manual missing permissions php post question section settings support test thread upgrade upload url vbulletin view
