Well, even if nothing else I am beginning to understand just how
complicated LiveCode
development is . . .
And all that I am twitched about at the moment is finding a properly
documented list of the conjunct
consonants for the Siddham writing system: suddenly my burden feels
about 1000 times lighter.
Richmond.
On 1/18/17 6:48 pm, panagiotis merakos via use-livecode wrote:
Hi Richmond,
Github shows all the bugs for which a PR has been submitted. So if no PR
has been submitted for a blocker, it will not show up.
The blocker Ali was referring to in his previous post is now fixed (
https://github.com/livecode/livecode/pull/5071).
However, unfortunately, yesterday we received a new bug report which turned
out to be a 8.1.2 RC-1 regression, thus a blocker for 8.1.3 RC-1, since our
goal is any regression introduced in LC X - RC to be fixed before LC X+1 RC.
Best regards,
Panos
--
On Wed, Jan 18, 2017 at 4:24 PM, Richmond Mathewson via use-livecode <
use-livecode@lists.runrev.com> wrote:
One thing I don't understand is, if there is a blocker, why it does not
show up
on Github:
https://github.com/livecode/livecode/milestone/126
I wonder if there is a way people like me can track all the dependencies (
i.e. those mentioned
inwith GitHub and those that seem to be outwith GitHub) so they can
guestimate a few things
about any deliverables they may have that are dependent on the delivery of
an upcoming
LiveCode build.
No; the peasants are not murmuring at my gates.
But, having got steam up after 2 years of slothlike development, it would
be nice
if I could give those who are interested a vague idea of a deliverable
date of a Beta
version of my next release (presumably it would be fairly daft to release
a finished
version, rather than a Beta version, on the basis of a LiveCode rlease
candidate).
Richmond.
On 1/13/17 1:02 pm, Ali Lloyd via use-livecode wrote:
We don't actually use GitHub milestones in that way, we just use them to
track which releases various pull requests have gone into. So 100%
complete
just means there are no outstanding pull requests with the 8.1.3-rc-1
milestone set.
As it happens, there is only one more blocker, unfortunately it is a
rather
tricky one. Once that is fixed and merged, a build will go through the
post-build test system and be released if it passes.
On Fri, Jan 13, 2017 at 8:43 AM Richmond Mathewson via use-livecode <
use-livecode@lists.runrev.com> wrote:
Wow;
https://github.com/livecode/livecode/milestone/126
"no due date"
100% complete
Ouch, I can feel the anticipation in the pit of my stomach.
Err: 100% Unicode functionality?
Richmond.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
