Subscription questions...

[Jose Lerebours]

So, is anyone up for a drink?  I have:

Crown
Crown Apple
Black Label
JW Gold
Chivas Regal
Jack Daniel
Jack Daniel Honey
Fireball
various Rums from around the world ... and Vodka, lots of Vodka.

I also have popcorn - at my age, soft drink by itself does not cut it!  ;-)

I mean, this is getting amusing and I'm suggesting we kick back and enjoy.


On 03/15/2016 05:39 PM, Fairlight via Filepro-list wrote:
> Do I even dignify this with a response?  Sure, why not?
>
> <deserved_irritation>
>
> WTF, Ken?  Seriously?
>
> You know damned well that I work for many clients who own one (or many)
> copies and versions of filePro.
>
> Whether the clients reported the bugs or not is on them, unless they ask
> me to do so.  I'm always happy to do so if it's asked of me, but it's not
> my job to go around cleaning up fP Tech's messes unless someone asks me to
> report he bugs, or fP Tech pays me to do so.  So no, I haven't -personally-
> supported tickets, even about bugs I know exist in 5.0.14.  That doesn't
> mean they don't exist.
>
> As I have made quite apparent, many people are averse to upgrading past
> 5.0.14 -anyway-, so reporting the bugs is pointless for those people to do,
> and has been for years.  It's not just pointless for me; it's pointless for
> them unless they want to play ball under the new model.  Many don't.
> Talking about 5.0.15 is akin to talking about 5.6, since it includes the
> license manager; 5.0.15 may as well not exist for those people, so it's
> never been an acceptable answer for them.
>
> Your response is disingenuous, at best.
>
> </deserved_irritation>
>
> mark->
>
> On Tue, Mar 15, 2016 at 12:02:06PM -0400, Kenneth Brody thus spoke:
>> On 3/14/2016 5:37 PM, Fairlight via Filepro-list wrote:
>> [...]
>>> This makes it clear that I'm not comfortable with the current release
>>> practises.  You have bugs left in 5.0.14/5.0.15 yet, and the only thing you
>>> do is point people towards the purchase page for the latest version.  It's
>>> not like the last 5.0 or even 5.6 were without bugs - sometimes even major
>>> ones.  I know of at least one major one to do with record locking and
>>> lookups.  Don't start me on blobs.
>> Can you tell me which bugs you have reported in 5.0 which are still
>> in 5.0.15?  Do you recall approximately when you reported them?
>>
>> If you have your account number, it may be easier for me to look up.
>> Or, better, the task number(s) you would have been given?
>>
>> (BTW, 5.0 is now over 15 years old.  Even the 5.0.15 update is over
>> 10 years old.)
>>
>> [...]
>>
>> -- 
>> Kenneth Brody
>>