GitHub issues

26 views
Skip to first unread message

Rob Beezer

unread,
Jul 24, 2026, 5:21:54 PMJul 24
to prete...@googlegroups.com
I'm teaching my assistant to triage the (huge) backlog of issues we have
accumulated (rather than relying on David Farmer, Alex Jordan, and others to do
it). So if something happens on an issue that is near-and-dear to you (like
being closed, when you think the explanation does not hold up), feel free to
re-open with a comment (or ask me to re-open it if you are not the owner).

Rob

Bradley Miller

unread,
Jul 24, 2026, 5:32:48 PMJul 24
to PreTeXt development
Great idea Rob!  I’d like to do that myself.  If you have a good prompt that you are using please share it with me.

Brad

Brad Miller
Professor Emeritus, Luther College
Founder, Runestone Academy LTD
Blog: http://reputablejournal.com

Set up a time to meet with me.


On Jul 24, 2026, at 4:21 PM, 'Rob Beezer' via PreTeXt development <prete...@googlegroups.com> wrote:

I'm teaching my assistant to triage the (huge) backlog of issues we have accumulated (rather than relying on David Farmer, Alex Jordan, and others to do it).  So if something happens on an issue that is near-and-dear to you (like being closed, when you think the explanation does not hold up), feel free to re-open with a comment (or ask me to re-open it if you are not the owner).

Rob

--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAxZU8uS1ZsLmw.1784928111%40pnsh.

Rob Beezer

unread,
Aug 9, 2026, 12:32:43 PMAug 9
to prete...@googlegroups.com
Open issues have dropped from about 600 down to 360. Still nothing to write
home about, but progress, and less embarassing. If you have been a big
contibutor to issues, you've likely seen a lot of traffic.

If something gets closed and you do not like (or agree with!) the resolution,
feel free to re-open or start a discussion here.

* Many have been closed because the root cause has eventually been addressed.

* Many have been closed with a "routine" amount of code from my assistant.
Please check these fixes if you were the original poster or an interested party.
A note to that effect on the issue would be a good record of the resolution.

* Some have been closed as "not actionable". A more targeted issue might be
more useful - please do that if you still see a need.

I will keep chipping away at these, but most of the low-hanging fruit is gone.

BTW, if you see a concrete improvement or a definite bug, a very clear
"pretext-dev" post, or an issue, can often be handled quite quickly now. My
assistant is quite good at bug-hunting.

Rob
Reply all
Reply to author
Forward
0 new messages