I'm a stupid GIT
richmondmathewson at gmail.com
Sat Jan 7 18:40:26 CET 2017
On 1/7/17 7:13 pm, Richard Gaskin via use-livecode wrote:
> Richmond Mathewson wrote:
> > How about an impatient chap whose GANTT chart of his 4th SDLC has
> > been completely thrown out of kilter owing to a bug (19045) in
> > existing builds of LiveCode, knowing that that bug has been sorted
> > out but that the next official RC build is waiting on at least
> > another 4 bugs being sorted out . . .
> > Am I daft to want to try to build an unofficial "8.1.2 and a half" to
> > see if the bug has really been sorted out, or would I be more
> > sensible to "bite down hard" and hang on for an official build?
> I guess that would depend on how comfortable you are in setting up the
> environment need to run the make file.
> I've not done it myself so I can't advise; maybe Mark Wieder or one of
> the core team folks can offer guidance if you get stuck.
> I should probably get around to setting that up myself sometime, but
> I'm a scripter at heart and do primarily UX/UI by trade, so it's been
> a low priority for me. And with the turnaround time the team's been
> doing lately, just about every time I think I may want to set that up
> a new build is available so I haven't needed to.
> I very much appreciate that the team often includes a link to the
> Github pull request in the Bugzilla report it relates to, such as this
> one Mark Waddingham included for #19045:
> I've found that reading the comments at those links can help me better
> understand the scope of a change.
> And when I see the Vulcan (automated test system) report "pass" I feel
> pretty confident it's gone well, such as we see there in a comment
> from two days ago:
> livecode-vulcan commented 2 days ago
> :sunglasses: test success 5deb2cd
> try-community-linux-x86: success
> try-community-mac: success
> try-community-linux-x86_64: success
> try-community-emscripten: success
> try-community-ios: success
> try-community-win-x86: success
> try-community-android-armv6: success
I also saw that and was impressed at the speed with which the team
sorted things out; that is why I am "slavering at the chops".
More information about the use-livecode