[APBeta] Expiration dates

[Steve Barkes]

Why not just set the expiration date to the date you expect to release the
production version?  You can change it later if it slips, and it probably
won't be released early ;-)  I think most of the beta testers are good at
downloading the latest version and won't be reporting bugs that have already
been squashed.

Steve


On 6/16/09 7:51 AM, "Paul Rodman" <paul at ilanga.com> wrote:

> 
> On Jun 16, 2009, at 5:56 AM, Michael Conte wrote:
> 
>> You and Robin make some valid points. I'm usually diligent in making
>> sure I have the latest and greatest but there have been times when
>> this has snuck up on me, usually when I haven't fired up AP on the
>> laptop for a week or two. As a beta tester, I at least know not to
>> report a problem unless I am running the latest version. I've spent
>> too many years working and programming computers not to understand
>> that requirement but can understand why that would be a concern for
>> others.
>> 
>> I intend to put 1.6 back on the machine for the very reasons
>> mentioned, however, "real" work in the field is the best test of the
>> application as far as I'm concerned, testing in combat stresses
>> everything including the operator! And, I find ver. 2 superior to
>> 1.6 (and I thought 1.6 was great so my hat off to Paul and all his
>> hard work) so that's my preferred version now. I maintain
>> complimentary versions of software applications on my laptop just in
>> case one crashes and burns for whatever reason so as long as the
>> laptop is running, I can switch to something else if necessary.
>> 
>> Maybe rather then bypassing the expiration date, a set number of
>> "grace" launches could be set up so that after two or three or five
>> (whatever value Paul feels is reasonable) then the app does die. Of
>> course, having the ability to use AP to download the latest version
>> is also an asset in case you don't have the appropriate book mark
>> set up in your browser.
>> 
>> However, I'm easy to get along with in most cases so whatever the
>> majority feels (and Paul decides) is appropriate is fine with me.
> 
> Well, how about a compromise:
> 
> The Expiration dialog has two buttons: Quit and Continue. The Quit
> button is enabled and is the default. The Continue button is disabled
> and only enabled after a countdown of 30 seconds. That should be
> irritating enough to promote a desire to download, and yet enables a
> lifeline for those times when you need one.
> 
> Paul R.
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net