[11:43:48] <pradyunsg> And that’s a question that we’ve been hitting a lot over the past few weeks, and is something that I’d like us (as a broader group) figure out the answer.
[11:44:03] <pradyunsg> I don’t even know if we want the final answer to be a compromise (read: everyone will be slightly unhappy) or a clearly opinionated choice (read: clear lines for what is "something else’s job").
[22:12:54] <sumanah> techalchemy: how you holding up?
[22:13:24] <sumanah> techalchemy: you wanna talk about it? I'm here (public, pm, videocall)
[22:14:07] <techalchemy> that was yet another week of azure-related failures it looks like, first because azure was doing things wrong before, and now because even though azure is still failing for no reason but github CI which i just added is now passing...
[22:15:37] <sumanah> techalchemy: it's been suggested that you cut another prerelease/beta, which, to me, sounds like a reasonable thing to do
[22:16:19] <sumanah> unless you would prefer to avoid "here's a beta I made despite CI flakiness"
[22:16:25] <techalchemy> yeah i can do that, depending on the rest of the night, i can attempt to do it today
[22:17:21] <techalchemy> there's one CI issue left but it's not one I am going to address, it's not really something the relevant library should support
[22:17:30] <sumanah> techalchemy: also: maybe I misunderstood something, but, it seemed like on Friday/Saturday you were ready to make a release. did something regress?
[22:19:36] <techalchemy> I was merging what should have been a simple fix in vistir to address #4195 but CI failed across the board for all kinds of strange reasons, but if cross platform / compatibility suport is broken in vistir it means it would be broken in pipenv (a consumer of vistir)
[22:20:54] <techalchemy> fairly sure at this point half of the issues were my fault for making some wrong assumptions which were exposed by a change in how azure is spinning up windows environments, while the other half is due to a change in the filesystem encoding on osx -- maybe?
[22:21:17] <sumanah> techalchemy: could you revert that change, and then release what was master at that moment?
[22:21:34] <techalchemy> i could rever it but that isn't what broke things
[22:21:44] <techalchemy> which is the bigger issue
[22:22:05] <sumanah> is there an artifact, which existed on Saturday morning, which you could release?
[22:23:07] <techalchemy> no? I was making this change as part of what should have been some quick revendoring in preparation to release
[22:23:54] <sumanah> ok, thanks, techalchemy, I had not understood
[22:24:13] <sumanah> do you need help making an update comment on the release tracking issue so people understand what they can expect next?
[22:25:06] <techalchemy> that'd be a massive help if you are up for it, i've been focused on trying to get everything together since I was already behind
[22:25:19] <techalchemy> but am acutely aware that some communication is necessary
[22:25:47] <sumanah> ok, techalchemy start up a collaborative document on Hackmd or Dropbox Paper or whatever you like and I'll make a quick outline/draft
[22:37:59] <techalchemy> sumanah, https://etherpad.wikimedia.org/p/pipenvupdate sorry forgot to paste it
[22:53:35] <sumanah> techalchemy: ok - so - my suggestion is that we work on this on the assumption that it will be a GitHub issue update, and then mention it in a quick note to the mailing lists