backup bouncer test suite

[jed]

I've just not used the product mate..
I'm a lot more committed to using a product it if I've paid for it, but..

I don't wont to pay for 2.5 only to be told shortly afterwards that a major new release is available "for a small upgrade fee".
I'd rather just pay for the major new release when it's available!

Can we expect a release this year, the latter half of next year, or later...
Large time windows are fine, don't have to give us an exact month etc.

-jed.

[dnanian]

Sorry: can't give a date. But as I said, we have never charged for an update, right?

[jed]

Lame, will prolly buy 2.5 then...

But I'll be peeved if I have to pay all over again.
Especially if it's this year..

tnx,
-jed.

[dnanian]

Lame? It's hard to understand how "every update that we've ever released, from 1.0 until 2.5, has been completely free to every user, and that we offer significant functionality that's been entirely free, with support, during all that time" is "lame", but everyone's entitled to their opinion, I guess, Jed!

[jed]

I was referring to the 'smoke n mirrors' with regards to release time-frame, nothing more.

I want the extra support/functionality, hence I have no problem with paying.
I just don't like buying into something when I have no way of knowing if there's a major update around the corner.

Especially if I have to pay again to get the 'new' extra functionality..

-jed.

[dnanian]

We just don't do "smoke and mirrors", Jed. Sorry: I don't think it benefits anyone.

[jed]

Dnanian, let me be more clear... What I meant by "smoke n mirrors is"...
Your developmental model is a lot more "under wraps" compared to other projects.

That's fine and entirely your choice...
Just be clear as early as possible what your plans are for the next major paid for release.

Otherwise you risk alienating people..