Formalizing preparing a release
164 views
Skip to first unread message
Matthias Bussonnier
Feb 8, 2017, 10:12:24 PM2/8/17
to jup...@googlegroups.com
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.
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.
Kyle Kelley
Feb 8, 2017, 10:14:08 PM2/8/17
to jup...@googlegroups.com
I'm certainly a fan.
For coordinated releases across multiple, I'd be happy with a meta
issue in the name/name package - ipython, ipykernel in
ipython/ipython; jupyter_client, notebook, etc. in jupyter/jupyter.
> --
> 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 jupyter+u...@googlegroups.com.
> To post to this group, send email to jup...@googlegroups.com.
> 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.
--
Kyle Kelley (@rgbkrk; lambdaops.com)
For coordinated releases across multiple, I'd be happy with a meta
issue in the name/name package - ipython, ipykernel in
ipython/ipython; jupyter_client, notebook, etc. in jupyter/jupyter.
> 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 jupyter+u...@googlegroups.com.
> To post to this group, send email to jup...@googlegroups.com.
> 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.
--
Kyle Kelley (@rgbkrk; lambdaops.com)
Thomas Kluyver
Feb 9, 2017, 6:52:58 AM2/9/17
to Project Jupyter
On 9 February 2017 at 03:12, Matthias Bussonnier <bussonnie...@gmail.com> 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. "
"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
Jason Grout
Feb 9, 2017, 8:05:24 AM2/9/17
to Project Jupyter
I think announcing and coordinating major (and probably even minor) releases in the way that Matthias outlines is a great idea. I agree with Thomas that bugfix releases should be easier and more frequently released.
--
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 jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAOvn4qg5gH%2BDLcFA%3D_TNBwqn0FQna9aD9BMTV_-tdHrWABLTfw%40mail.gmail.com.
Carol Willing
Feb 9, 2017, 9:12:28 AM2/9/17
to jup...@googlegroups.com
It would be a good idea to
include a tentative release calendar at the bottom of the weekly
development update that Matthias has been helpfully sending to this
list. Capturing information in a release planning table would be
beneficial; it would have been hugely helpful last year for planning
documentation efforts. Information could include:
- Project name with link to repo
- Current stable release version and date released
- In progress release type (major, minor, bugfix), version, and
projected week of beta/release
February 9, 2017 at 5:05 AM
I think announcing and coordinating major (and probably even minor) releases in the way that Matthias outlines is a great idea. I agree with Thomas that bugfix releases should be easier and more frequently released.
--
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 jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAPDWZHwSPDWDqGJe%3DMd5VJCwMyNEdoZuz39RcrCGfGz3sJVUYw%40mail.gmail.com.
February 9, 2017 at 3:52 AM
--On 9 February 2017 at 03:12, Matthias Bussonnier <bussonnie...@gmail.com> 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 jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
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.
February 8, 2017 at 7:12 PM
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.
Brian Granger
Feb 9, 2017, 1:59:22 PM2/9/17
to Project Jupyter
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.
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgra...@calpoly.edu and elli...@gmail.com
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.
> --
> 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 jupyter+u...@googlegroups.com.
> To post to this group, send email to jup...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CANJQusV%3DVYmhw%2B5mAGYPx6MHLDXyL9tfNqvTvftM%2BOa2g0m9Hg%40mail.gmail.com.
> 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 jupyter+u...@googlegroups.com.
> To post to this group, send email to jup...@googlegroups.com.
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgra...@calpoly.edu and elli...@gmail.com
Steven Silvester
Feb 9, 2017, 8:59:08 PM2/9/17
to Project Jupyter
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.
MinRK
Feb 10, 2017, 10:06:38 AM2/10/17
to Project Jupyter
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
--
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 jupyter+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/15e15697-328a-4903-882b-5c1506bee00a%40googlegroups.com.
Jason Grout
Feb 10, 2017, 5:36:04 PM2/10/17
to Project Jupyter
It would be great if we could automate that page showing unreleased commits in each project. I really like that.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/15e15697-328a-4903-882b-5c1506bee00a%40googlegroups.com.
--
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 jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAHNn8BW-0igAyPeSkKJSm9bAR7TkCwwsE-Kdz75iHX0RVL5qxQ%40mail.gmail.com.
Thomas Kluyver
Feb 11, 2017, 6:16:08 AM2/11/17
to Project Jupyter
I'm assuming it's already automated? I also like that page; I have trouble remembering the release status of different projects.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/15e15697-328a-4903-882b-5c1506bee00a%40googlegroups.com.
--
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 jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
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 jupyter+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAPDWZHwS6igd6Lf4JuEw5M%3DFNo_PUsJ%3D%2BD2tdykQoTi1bLU8QA%40mail.gmail.com.
MinRK
Feb 13, 2017, 4:51:52 AM2/13/17
to Project Jupyter
On Sat, Feb 11, 2017 at 12:15 PM, Thomas Kluyver <tak...@gmail.com> 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
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAOvn4qhDRny5AmC08U5D79R%2BN9hEiwKsy1VAK9ax-q2JqRz6rw%40mail.gmail.com.
Brian Granger
Feb 19, 2017, 2:01:42 PM2/19/17
to Project Jupyter
I teach during the dev meetings this quarter. Was a decision reached on this?
>>>>> an email to jupyter+u...@googlegroups.com.
>>>>> To post to this group, send email to jup...@googlegroups.com.
>>>>> 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 jupyter+u...@googlegroups.com.
>>>>> 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
>>>> To post to this group, send email to jup...@googlegroups.com.
>>>> 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 jupyter+u...@googlegroups.com.
>>>> 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
>>> To post to this group, send email to jup...@googlegroups.com.
>>> 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 jupyter+u...@googlegroups.com.
>>> 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
>> To post to this group, send email to jup...@googlegroups.com.
>> 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.
>
>
>> 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 jupyter+u...@googlegroups.com.
> 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
> To post to this group, send email to jup...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAHNn8BUhgPCYSmeSWuuP5c0KKNM%3D2u7Rb-mRO-MK6P_QNq%3DvMQ%40mail.gmail.com.
> To view this discussion on the web visit
MinRK
Feb 20, 2017, 2:25:18 PM2/20/17
to Project Jupyter
On Sun, Feb 19, 2017 at 8:01 PM, Brian Granger <elli...@gmail.com> wrote:
I teach during the dev meetings this quarter. Was a decision reached on this?
We didn't formalise a process, but we did come up with a few things:
1. open an Issue on the package's repo to track preparing for a large release, tagging Jamie for project management
2. solicit input / testing on the mailing list
3. keep the process light for the smaller releases and repos
-Min
>>>>> an email to jupyter+unsubscribe@googlegroups.com.
>>>>> To post to this group, send email to jup...@googlegroups.com.
>>>>> 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 jupyter+unsubscribe@googlegroups.com.
>>>> To post to this group, send email to jup...@googlegroups.com.
>>>> 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 jupyter+unsubscribe@googlegroups.com.
>>> To post to this group, send email to jup...@googlegroups.com.
>>> 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 jupyter+unsubscribe@googlegroups.com.
>> To post to this group, send email to jup...@googlegroups.com.
>> 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 jupyter+unsubscribe@googlegroups.com.
> To post to this group, send email to jup...@googlegroups.com.
> 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
bgra...@calpoly.edu and elli...@gmail.com
--
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 jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH4pYpTqUYf-uVdWoZfGFd1modLuPcrwiVgH6-%3DmF_ivGD%2Bimg%40mail.gmail.com.
Brian Granger
Feb 21, 2017, 9:29:03 AM2/21/17
to Project Jupyter
Thanks for the update, sounds good!
>> >>>>> an email to jupyter+u...@googlegroups.com.
>> >>>>> To post to this group, send email to jup...@googlegroups.com.
>> >>>>> 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 jupyter+u...@googlegroups.com.
>> >>>>> 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
>> >>>> To post to this group, send email to jup...@googlegroups.com.
>> >>>> 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 jupyter+u...@googlegroups.com.
>> >>>> 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
>> >>> To post to this group, send email to jup...@googlegroups.com.
>> >>> 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 jupyter+u...@googlegroups.com.
>> >>> 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
>> >> To post to this group, send email to jup...@googlegroups.com.
>> >> 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 jupyter+u...@googlegroups.com.
>> >> 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
>> > To post to this group, send email to jup...@googlegroups.com.
>> > 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
>> bgra...@calpoly.edu and elli...@gmail.com
>>
>> --
>> 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 jupyter+u...@googlegroups.com.
>> > 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
>> bgra...@calpoly.edu and elli...@gmail.com
>>
>> --
>> 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
>> To post to this group, send email to jup...@googlegroups.com.
>> 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.
>
>
>> 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.
>
>
> --
> 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 jupyter+u...@googlegroups.com.
> 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
> To post to this group, send email to jup...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jupyter/CAHNn8BUfoMrDesJpxCT2G8K6L0gtiQXuUiA4nsrXJ%2BchhwptrQ%40mail.gmail.com.
> To view this discussion on the web visit
JamieW
Feb 21, 2017, 6:48:29 PM2/21/17
to Project Jupyter, elli...@gmail.com
Thanks Min. Mentioning me in the issue- even though a human step- seems to be working so far. I'm also performing a periodic sweep for issues with "Release" in the title and adding these issues to the Jupyter Org's GitHub Projects trial release calendar : https://github.com/orgs/jupyter/projects/4. This only covers releases posted in the Jupyter Org and not other orgs.
Looking forward to finding ways to automagically track releases across orgs! = )
Reply all
Reply to author
Forward
0 new messages