On Mon, Apr 2, 2018 at 11:09 AM, Eric Gourgoulhon <egourgoul...@gmail.com> wrote: > Since we have entered the 8.2.rc cycle, may I ask about the status of the > (blocker) ticket #24484 (broken export of Jupyter notebooks to any format) > ? > Without it, many users might complain (it was working fine in Sage 8.1).
I'll see if I can work on finishing it, and hopefully we can get that in the next "rc". If it is in fact a blocker it should be treated as such. The raft of "last minute" issue requests for 8.2 appearing in this thread indicates to me once again the problems with Sage's release scheduling, or lack thereof. Without more communication / planning of Sage releases no one really "knows" for sure when a Sage release is imminent until some commit happens to get tagged "rc". *Then* it becomes a panic of "oh, those issues I haven't been working on (because I was busy with other things, etc.) are suddenly higher priority", because otherwise they won't be in a final release until after the next 3+ month development cycle. I think this can be mitigated significantly simply by having a rough, but published release cycle (say, one every 3 months), with cutoff dates for non-critical issues, and reminders (to this list) of those cutoff dates so that any people can have a chance to advocate for and/or complete work that they hope to see in the release *before* we start tagging things as "release candidates". Best, E -- 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.
