I am definitely in favor of this. We have millions of users, with many of them organizations, universities, non-profits, researchers, etc. who are relying on our software and building on top of it. So, in addition to our own developers needing to know about and discuss releases, we also have a broader set of stakeholders who are affected by upcoming releases.
Many of these stakeholders don't follow our weekly meetings/notes closely and wouldn't be able to follow all of our repos (even our core devs working full time are not able to follow these things). Because of that a post on the mailing list about each major release is about as good as we can do to let the community know a release is approaching. In terms of where to open an issue, I almost think the project management repo makes sense: https://github.com/jupyter/project-mgt That is a great way of keeping Jamie in the loop on these things. But I am also fine with using other repos for the issues. On Wed, Feb 8, 2017 at 7:12 PM, Matthias Bussonnier <[email protected]> wrote: > Hello all, > > It recently came to the attention to some of us that with the > increasing number of projects we have it can be hard to follow when > packages are going to be released, which often leads to very short > windows of time to give feedback or test the new version with existing > software. > > 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. > > 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. > > That would be of course on a per-project/per-maintainer basis, but the > project would try to encourage it for major releases, or maybe even > minor releases. > > Thanks, > -- > Matthias, with the help of Jamie, Jason, Brian and Fernando. > > -- > 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/CANJQusV%3DVYmhw%2B5mAGYPx6MHLDXyL9tfNqvTvftM%2BOa2g0m9Hg%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub [email protected] and [email protected] -- 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/CAH4pYpQ7L8MCk%2Bm16nDZE0HqDje-s4ey%2ByH7d-kU4gDoETaQNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
