I hear you on marking milestones and wishful thinking. That's how I feel
about the "due dates" on most requests I receive at work ;-)
*>... those items that I definitely want to finish (or close) before 5.7.*
Which brings up a question I've been meaning to ask: is the work that's
happening right
Git issues gives us lots of flexibility for marking issues in various ways.
In the past, I've tended to mark all items as having a milestone for the
next release. But that's unhelpful wishful thinking.
So now I've only give milestones to those items that I definitely want to
finish (or close)
On Saturday, November 11, 2017 at 12:41:34 PM UTC-6, Terry Brown wrote:
>
> One impediment to routinely running unit tests is that they seem to be
> render your computer unusable for the time they take to run.
True, but that shouldn't be a good enough excuse for not running unit tests.
#503:
One impediment to routinely running unit tests is that they seem to be
render your computer unusable for the time they take to run. Even when
I have enough screen real-estate to run them out the way, I'm worried
they'll grab focus while I'm working on something else and (a) I'll
cause a test to
On Friday, November 10, 2017 at 3:24:57 AM UTC-6, Edward K. Ream wrote:
> Imo, it's time for me to fix about a dozen long-standing bugs,
high-priority bugs, as shown on this page
On Sat, Nov 11, 2017 at 1:15 AM, Matt Wilkie wrote:
So where does this leave us?
>
>-
>
>Do nothing. In it's current state pip install Leo succeeds, the end
>user has a fully functioning application (so far as we know, given the
>light testing to date), but some
On Fri, Nov 10, 2017 at 6:38 PM, Terry Brown wrote:
What about f432d7d8, importing editpane now how no side effects, does
> @test leoBridge work now?
>
> Or does leoBridge require the modules that can't run without Qt not
> attempt to run?
>
Is there some reason you