[APBeta] Expiration dates

[Paul Kemp]

Yep,

Hard limits are good and agree with the policy. You should upgrade to the
latest beta as soon as it comes out.

I had a major issue with a beta version about 8 weeks ago and need to run a
previous version, but only till the problem was sorted. Paul is great and
wants to understand any issue that a user is having....knowing that any
problem is likely to affect a greater amount of 'paying' customers later.

Beta testing is great, you get to participate in the next version of a
program, but can snag you when something does not work properly. I am so
used to APv2.0 now that going back to v1.6 would annoy me intensely.
However, it is a Beta, expect the unexpected.

Paul Kemp
13.1" f5 Reflector with Argo Navis & Paracorr
Auckland, New Zealand
36° 55' 09" South, 174° 43' 30" East

--- The Southern Sentinel ---
www.southernsentinel.co.nz

Checkout my Twitter: twitter.com/pulinski


On Tue, Jun 16, 2009 at 5:10 PM, Michael Portuesi <portuesi at jotabout.com>wrote:

> Robin,
>
> I agree with you.
>
> I'd also point add two things to Robin's well-reasoned message:
>
> 1) If you're a beta tester, you should always be on the latest version
> unless there's a good reason otherwise.  If you're not running the latest,
> you're not in a good position to submit bug reports - which is what being a
> beta tester is all about.
>
> If the original poster had followed that rule, AP would not have crapped
> out for him in the field, because Paul releases a new beta almost every
> week.
>
> 2) You shouldn't be depending solely upon beta software to do "real" work
> in the field.  Even if the expiration hadn't kicked in, a critical bug could
> also have brought an end to the evening's observing.  It's quite easy to
> have AP 1.x (stable) and 2.x (beta) on the same machine.
>
> I'm another person who thinks Paul should leave the hard expiry limit in.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.astroplanner.net/pipermail/apbeta-astroplanner.net/attachments/20090616/3a05580d/attachment-0003.htm>