While I agree that the Cygwin/Windows port is somewhat neglected in this current release cycle, how about a Cygwin patchbot/buildbot?
I see https://patchbot.sagemath.org/?machine=CYGWIN_NT-10.0&machine=2017-04-01%2020:47&machine=x86_64&machine=2.8.0(0.309/5/3)&machine=windows-10-prof&status=needs_review but is it alive and kicking? On Tuesday, December 5, 2017 at 5:24:19 PM UTC, Erik Bray wrote: > > On Tue, Dec 5, 2017 at 6:16 PM, Emmanuel Charpentier > <[email protected] <javascript:>> wrote: > > > > > > Le mardi 5 décembre 2017 18:03:19 UTC+1, Dima Pasechnik a écrit : > >> > >> The skylake wait was due to a bunch of active Sage users and devs > needing > >> it and asking for it. > >> > >> Perhaps we should aim at 8.1.1 with Cygwin fix? > > > > > > The attention to Cygwin is indeed justified by the hope of getting > *new* > > Sage users (namely Windows 10 users). > > But I note that Trac#24121 has been positively reviewed for 4 weeks, > whereas > > Trac#21233 has got positive review "only" 13 days ago. > > It originally had "positive review" 5 months ago, then Volker set it > back to "needs work" due to a seemingly-related test that was failing. > In fact as far as I can tell that test was not directly related to my > fix, and was already broken due to a random nature of it, and it just > happened to fail (possibly my changes made it more likely to fail due > to entropy :). I immediately corrected this and set it back to "needs > review", and then nothing... > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
