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
I would recommend keeping it simple by incorporating it into our weekly
workflow for the development meeting.
Jason Grout <mailto:[email protected]>
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 [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jupyter/CAPDWZHwSPDWDqGJe%3DMd5VJCwMyNEdoZuz39RcrCGfGz3sJVUYw%40mail.gmail.com
<https://groups.google.com/d/msgid/jupyter/CAPDWZHwSPDWDqGJe%3DMd5VJCwMyNEdoZuz39RcrCGfGz3sJVUYw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
Thomas Kluyver <mailto:[email protected]>
February 9, 2017 at 3:52 AM
On 9 February 2017 at 03:12, Matthias Bussonnier
<[email protected] <mailto:[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]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[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
<https://groups.google.com/d/msgid/jupyter/CAOvn4qg5gH%2BDLcFA%3D_TNBwqn0FQna9aD9BMTV_-tdHrWABLTfw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
Matthias Bussonnier <mailto:[email protected]>
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.
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,
--
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/589C78C7.9070800%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
