Zippy-da-doo-dah 8.1.3

[Ali Lloyd]

The reason it doesn't show up on GitHub is that it will only appear on
GitHub when there is a pull request, which is usually only when it is
fixed. What you need is

http://quality.livecode.com/buglist.cgi?list_id=67534&query_format=advanced&target_milestone=8.1.3-rc-1

Not everything in that list actually blocks, so try:

http://quality.livecode.com/buglist.cgi?list_id=67534&query_format=advanced&target_milestone=8.1.3-rc-1&bug_severity=blocker

The previous blocker I mentioned is now fixed, but there is a critical
issue with the tsNet external that is now blocking the release. That is one
of the unfortunate things about blockers - they can delay the release long
enough to allow more blockers to show up. Of course at some point you have
to draw a line, but the aformentioned bug is well beneath* it.

*I'm not sure when you metaphorically draw a line, whether that line is
meant to be horizontal or vertical, or indeed which side of the line you
start from

On Wed, Jan 18, 2017 at 4:24 PM Richmond Mathewson via use-livecode <
use-livecode at 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 at 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 at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>