Seeking confirmation of a bug...
brian at milby7.com
Sat May 18 18:39:14 EDT 2019
Looking at the beginning of the thread, I think what Richard meant initially is that if everyone always moved to the latest version (bonus for testing with RC and DP versions) then regressions would probably be spotted fairly quickly since a vast surface area of the engine would be tested at once. Just knowing what stopped working on your app would be helpful to the dev team.
On May 18, 2019, 4:31 PM -0400, Curry Kenworthy via use-livecode <use-livecode at lists.runrev.com>, wrote:
> > Two very different scenarios. What you describe is what I often
> > see Panos and others deliver in the course of resolving reports,
> > identifying the source of origin of a bug.
> And now three different scenarios! Not at all what I described.
> > For us, if we encounter a bug all we need to do is to report it
> You can't report what you never notice. That is, again, the crux.
> The first step or reporting a bug is to be aware of it. No way around
> it. And with regressions (except for the most obvious) that means
> noticing change. Therefore to actually find more regressions:
> Install the latest build AND an older version! :)
> Best wishes,
> Curry Kenworthy
> Custom Software Development
> "Better Methods, Better Results"
> LiveCode Training and Consulting
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode