I teach during the dev meetings this quarter. Was a decision reached on this?
On Mon, Feb 13, 2017 at 2:51 AM, MinRK <[email protected]> wrote: > > > On Sat, Feb 11, 2017 at 12:15 PM, Thomas Kluyver <[email protected]> wrote: >> >> I'm assuming it's already automated? I also like that page; I have trouble >> remembering the release status of different projects. > > > The page is updated automatically. The only thing that's not automated is > the list of repos, which it could get programmatically by checking for all > repos on our orgs that have at least one tag. > > -Min > >> >> On 10 February 2017 at 22:35, Jason Grout <[email protected]> wrote: >>> >>> It would be great if we could automate that page showing unreleased >>> commits in each project. I really like that. >>> >>> On Fri, Feb 10, 2017 at 10:06 AM MinRK <[email protected]> wrote: >>>> >>>> I made this PR earlier this week to get ready to release jupyter-core >>>> 4.3. It is a tiny release (add support for one environment variable). Is >>>> there anything more that I should do before cutting that release? >>>> >>>> I just opened this issue for releasing jupyter-client 5.0. It is a major >>>> version bump due to a technically backward-incompatible change >>>> (timezone-aware datetime objects), but it is still a ‘small’ release, since >>>> that is in a feature that is rarely used (only in IPython parallel, to my >>>> knowledge, which already supports the changes in master). Should I open an >>>> issue on project-mgt about this? >>>> >>>> I think a release calendar is tough for many repos, as most won’t have >>>> planned releases until a certain amount of changes have been accumulated. >>>> Communicating upcoming major releases for the bigger user-facing projects >>>> (notebook, ipython, nbconvert) is definitely important. The mailing list >>>> seems like the most logical place to signal "We're trying to get ready for >>>> release, please help with extra testing, catching regressions, etc." that >>>> should catch people who don't follow GitHub issues. >>>> >>>> I made this page as an exercise a while ago, which summarizes how much >>>> we have that’s unreleased. It doesn’t give an indicator of how close we are >>>> to any given release, but it does (roughly) indicate how much we have >>>> unreleased, which can be used as a reminder to start pushing toward a >>>> release, especially on the easily forgotten smaller repos. >>>> >>>> -Min >>>> >>>> On Fri, Feb 10, 2017 at 2:59 AM, Steven Silvester >>>> <[email protected]> wrote: >>>>> >>>>> I like the idea of handling the tracking and coordination on the >>>>> https://github.com/jupyter/project-mgt and having a snapshot in the weekly >>>>> dev meeting report as well. >>>>> >>>>> >>>>> >>>>> On Wednesday, February 8, 2017 at 9:12:24 PM UTC-6, Matthias Bussonnier >>>>> 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/15e15697-328a-4903-882b-5c1506bee00a%40googlegroups.com. >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> 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/CAHNn8BW-0igAyPeSkKJSm9bAR7TkCwwsE-Kdz75iHX0RVL5qxQ%40mail.gmail.com. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> 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/CAPDWZHwS6igd6Lf4JuEw5M%3DFNo_PUsJ%3D%2BD2tdykQoTi1bLU8QA%40mail.gmail.com. >>> >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> 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/CAOvn4qhDRny5AmC08U5D79R%2BN9hEiwKsy1VAK9ax-q2JqRz6rw%40mail.gmail.com. >> >> For more options, visit https://groups.google.com/d/optout. > > > -- > 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/CAHNn8BUhgPCYSmeSWuuP5c0KKNM%3D2u7Rb-mRO-MK6P_QNq%3DvMQ%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/CAH4pYpTqUYf-uVdWoZfGFd1modLuPcrwiVgH6-%3DmF_ivGD%2Bimg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
