Almost every update is just some fixes...

Last update was on March 26th, where did you get 12 months from?!

You are getting us excited again...
What's coming?

I think I'm in love .....

Bug fixes should not be mistaken or mislabeled as updates.

It is my opinion that a member's entitlement to 12 months upgrades should be reviewed, and replaced with a number of, using version 2 numbering, 2.x.n, where x = an upgrade = new features, whilst n = bug fixes and should be free to all and anyone, regardless.

A member's 12 months of free upgrades could simply be used up with 12 months of bug fixes, and in reality many bug fixes are worked out by the forum/user community.

While bug fixes are released as version upgrades, the member's 12 months slips past (that's where I get my 12 months from)

Buy the system, get 2~3 N.X.n free upgrades (X being the minor version), or even N should it happen, whether that be 12 months of 24 months, and after that, pay for any X upgrade.

It is not an easy fix, and would require some methodical implementation, but in the end would make for a fairer system = happy customers = repeat customers.

The upgrade should reflect and equate to features, not time.
I feel this is why some, not all, but some, members stay with older releases.

This post is meant as a qualified opinion, not a random argument, or one designed to incite a hotly debated topic.

[soapbox stand re: qualified opinion]

I have been a programmer on and off for the past 17 years, and have lived/worked in 3 countries, over 3 continents. I wonder how many could say the same in terms of experience.

I make this post, and say this, not to big note myself, but to try and lend some credence to my experience with companies who plan, and some who make wild promises to customers whilst unaware of what programmers are doing,as I have experienced both, and some in-between.

One customer in Los Angeles had been made wild promises, billed multiple times for work not completed, and had a "system" that on my first visit to her with the company, was being compiled in the car as we drove to her office. What a Mickey Mouse outfit (M****z, San Diego)
That irate customer became my first client with the company I worked for - I had been thrown to the wolves, as she freely admitted she had become, and it was my job to placate her, and give her something that worked, at a fair price. She later asked me to join her company.

[/soapbox stand]

Last edited by fatlizard (2010-07-21 09:09:26)

i thin kit should be like this,
create a new forum section inside private lounge, call it: Bugs & Fixes

only staff could post here for example or maybe only staff can open topics and members can only reply

So for example there is a new bug in chat for example
staff finds out about it themselves or from us the clients,
then they make a topic something like this:

Bug Chat Block Issue v.2.5.6(version info) & Fix

then the post should something like

Hello,
We have discovered a bug in version 2.5.6 of vldpersonals
The bug consists in ... and some description of what the issue is

And after the bugfix
Like: replace in file x lines 123 with the following code

and to be on the safe side for those who have changes done to the files post the lines that need replaced too

like:
replace lines:
abc > 2
with
abc = 2

this will not force users to wait for a new version release to fix some bugs and will be good for those with changes done to their websites.
and also this way when vld releases a new version it should only have additions since all the bugs will be found & fixed on the way using the new forum

just my 1 cent