On 9 February 2017 at 03:12, Matthias Bussonnier < [email protected]> wrote:
> For example, several developers were surprised yesterday with the > announcement of an upcoming notebook 5.0 release, and are now > struggling to catch up on what is new and to test their > plugins/extensions. There are likely others in the community who did > not realize the 5.0 release was so close, who would need some time to > test their extensions/plugins and give feedback. > The notes from last week's meeting do say: "Currently going through issues to try to get 5.0 out as soon as possible. Hopefully Beta next month. " So this shouldn't have come as a total surprise. How would the team and everyone else feel if we encouraged Jupyter > projects to open an issue when a major release started to take shape > which clearly listed the planned schedule for the release and > highlighted what was new in the release? The upcoming release and this > issue would be announced on the mailing list. People interested in > following the release updates could subscribe to this issue. I think this makes sense for something like a major release of notebook. Not so much for minor releases, or less prominent packages. I'd actually like minor releases to involve fewer steps - this has been very noticeable doing bugfix releases of IPython, where the release process doc lists 14 steps. Thomas -- You received this message because you are subscribed to the Google Groups "Project Jupyter" 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAOvn4qg5gH%2BDLcFA%3D_TNBwqn0FQna9aD9BMTV_-tdHrWABLTfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
