On Saturday, April 21, 2018 at 1:28:18 AM UTC-7, Volker Braun wrote: > > At the end of the day, this just wastes some time on initial build -> not > a blocker. If somebody comes up with a fix in the next 24h I'll merge it. >
Has the CEO declared some deadline for the release? I must have missed that. Otherwise, why release flawed software that will inconvenience anyone building on OS X? It's the second build, not the initial build – if you don't remember that it's an issue, it's the second build. So the typical workflow will be: run make, switch to another branch to do some development, run make again, at which point you have to wait for an hour and half even though you just touched one py file. So as long as this is a bug, you have to run make twice to get something usable for development. -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
