Imo, using TravisCI provides no significant testing benefits, slows the 
commit process,  and creates unnecessary (and confusing) distribution files.

Instead, devs need only ensure that Leo's test-all command succeeds before 
each commit.

Two recent issues have severely tested my tolerance for TravisCI:

1. TravisCI creates leo.exe, which imo should be hidden but somehow got 
documented here <https://leoeditor.com/download.html#standalone>. See #2370 
<https://github.com/leo-editor/leo-editor/issues/2370>.

2. Within the last several days, TravisCI has suddenly started rejecting 
*all* commits, even those based on master, which hasn't changed in over a 
month.  See #2421 <https://github.com/leo-editor/leo-editor/issues/2421>.

Folks, I think it's time to do without TravisCI. Your comments, please.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/29296a9e-fe6b-45e2-98bb-6015248e246an%40googlegroups.com.

Reply via email to