On Sat, May 5, 2018 at 10:21 PM, <nbr...@sfu.ca> wrote: > On Thursday, April 26, 2018 at 7:11:52 AM UTC-7, Erik Bray wrote: >> >> >> Given such a branch to work in, it becomes less "urgent" to finish a >> release since it no longer needs to block normal development progress. >> Of course, you still don't want to spend forever getting a release >> out, but at least the release itself doesn't become a blocker. >> > Having some urgency to completing a release once it's decided to start it is > probably beneficial as a whole. > > However, in the current situation we've have sage8.2rc0 more than a month > ago and progress on the development branch is at a complete standstill at > the moment. I don't think this is healthy for the project. I don't have the > time or expertise to help with that myself, but I hope others do and are > able to dislodge the current jam.
My suggestion for how to resolve this seems obvious and straightforward. The only objection I've seen is "but what will the patchbots do?" But with a better documented process that is easily resolved. If it's not clear, shall I write up some more formal documentation for my proposed process? -- 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.
