Anticipated timeframes for milestones

Community Support
1

Hi all,

I’m wondering if I’ve missed a wiki page or a piece of documentation that outlines the timeframe for milestones.

The main place I would expect to see it is: Milestones - bokeh/bokeh · GitHub

I get the sense from comments on the issues that there is some shared understanding about timeframes amongst the core devs.

When thinking about PR I might like to do, it’s really great to know what the schedule is looking like, and when the code freezes will be.

I know the project is moving really fast and sometimes there’s a need for a quick release or things get delayed, so I don’t have strong expectations that these things will be rigid, but some guidance would be useful.

Best,

Bird

2

You probably need to take a look at:

1- http://bokeh.pydata.org/en/latest/docs/release_notes.html#roadmap

2- https://github.com/bokeh/bokeh/wiki/BEP-1:-Issues-and-PRs-management#issue-times

But we also probably need to make public code-freeze dates, estimated release dates, etc, at least after we effectively decide when it will be :wink:

···

On Thu, Feb 19, 2015 at 1:39 PM, Sarah Bird [email protected] wrote:

Hi all,

I’m wondering if I’ve missed a wiki page or a piece of documentation that outlines the timeframe for milestones.

The main place I would expect to see it is: https://github.com/bokeh/bokeh/milestones

I get the sense from comments on the issues that there is some shared understanding about timeframes amongst the core devs.

When thinking about PR I might like to do, it’s really great to know what the schedule is looking like, and when the code freezes will be.

I know the project is moving really fast and sometimes there’s a need for a quick release or things get delayed, so I don’t have strong expectations that these things will be rigid, but some guidance would be useful.

Best,

Bird

–

You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” 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/a/continuum.io/d/msgid/bokeh/3cfaf20b-0976-49eb-a535-a84afea41d50%40continuum.io.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

3

Yes, have read the above, and was looking for something more specific.

I noticed today, for example, Bryan mentioned on a ticket “why not leave this for 0.8.2?” and Mateusz replied quickly “Just clicked 0.8.1 too eagerly.” - to my reading this implies a whole level of understanding about a plan, that as an outside contributor, I don’t have, and I don’t get from the above links either.

Maybe you see it there and I’m just missing something in plain sight, in which case, I greatly appreciate your patience.

···

On Thu, Feb 19, 2015 at 9:47 AM, Damian Avila [email protected] wrote:

You probably need to take a look at:

1- http://bokeh.pydata.org/en/latest/docs/release_notes.html#roadmap

2- https://github.com/bokeh/bokeh/wiki/BEP-1:-Issues-and-PRs-management#issue-times

But we also probably need to make public code-freeze dates, estimated release dates, etc, at least after we effectively decide when it will be :wink:

–

You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” 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/a/continuum.io/d/msgid/bokeh/CAM9Ly3EXe1R5WKaTH-Ud0K_E1c0cY%2BzLY2CacE1QL0hzhyPqmQ%40mail.gmail.com.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

On Thu, Feb 19, 2015 at 1:39 PM, Sarah Bird [email protected] wrote:

Hi all,

I’m wondering if I’ve missed a wiki page or a piece of documentation that outlines the timeframe for milestones.

The main place I would expect to see it is: https://github.com/bokeh/bokeh/milestones

I get the sense from comments on the issues that there is some shared understanding about timeframes amongst the core devs.

When thinking about PR I might like to do, it’s really great to know what the schedule is looking like, and when the code freezes will be.

I know the project is moving really fast and sometimes there’s a need for a quick release or things get delayed, so I don’t have strong expectations that these things will be rigid, but some guidance would be useful.

Best,

Bird

–

You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” 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/a/continuum.io/d/msgid/bokeh/3cfaf20b-0976-49eb-a535-a84afea41d50%40continuum.io.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

4

In fact we found some subtle bugs in the last release and the we plan to release 0.8.1 very soon… but previously 0.8.1 would be released several weeks ahead… we just made a quick move to solve these issues and release 0.8.1 early to prevent people problems with the last release… as I said, we are having more and more contributors (as you) and we probably need to give you this info as soon as we have it…

···

On Thu, Feb 19, 2015 at 2:55 PM, Sarah Bird [email protected] wrote:

Yes, have read the above, and was looking for something more specific.

I noticed today, for example, Bryan mentioned on a ticket “why not leave this for 0.8.2?” and Mateusz replied quickly “Just clicked 0.8.1 too eagerly.” - to my reading this implies a whole level of understanding about a plan, that as an outside contributor, I don’t have, and I don’t get from the above links either.

Maybe you see it there and I’m just missing something in plain sight, in which case, I greatly appreciate your patience.

–

You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” 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/a/continuum.io/d/msgid/bokeh/CA%2BEr%2BdQGoFCGZSWKPt3my2a%3D9wuROeh%2B446rWuakeB8mtVPKFw%40mail.gmail.com.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

On Thu, Feb 19, 2015 at 9:47 AM, Damian Avila [email protected] wrote:

You probably need to take a look at:

1- http://bokeh.pydata.org/en/latest/docs/release_notes.html#roadmap

2- https://github.com/bokeh/bokeh/wiki/BEP-1:-Issues-and-PRs-management#issue-times

But we also probably need to make public code-freeze dates, estimated release dates, etc, at least after we effectively decide when it will be :wink:

–

You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” 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/a/continuum.io/d/msgid/bokeh/CAM9Ly3EXe1R5WKaTH-Ud0K_E1c0cY%2BzLY2CacE1QL0hzhyPqmQ%40mail.gmail.com.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

On Thu, Feb 19, 2015 at 1:39 PM, Sarah Bird [email protected] wrote:

Hi all,

I’m wondering if I’ve missed a wiki page or a piece of documentation that outlines the timeframe for milestones.

The main place I would expect to see it is: https://github.com/bokeh/bokeh/milestones

I get the sense from comments on the issues that there is some shared understanding about timeframes amongst the core devs.

When thinking about PR I might like to do, it’s really great to know what the schedule is looking like, and when the code freezes will be.

I know the project is moving really fast and sometimes there’s a need for a quick release or things get delayed, so I don’t have strong expectations that these things will be rigid, but some guidance would be useful.

Best,

Bird

–

You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” 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/a/continuum.io/d/msgid/bokeh/3cfaf20b-0976-49eb-a535-a84afea41d50%40continuum.io.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.

5

Hi Sarah,

Sorry for the late reply, I have been out on travel.

As you may know, up until very recently all of the core Bokeh devs have been affiliated with Continuum one way or another. And you are quite correct about OOB communication: we have a google hangout every week to discuss the project status and progress. Now that Bokeh is attracting outside contributors, we will need to find ways to integrate them better into the team. As Damian mentioned, we should publicized release estimates, etc., better, but in fact I think we should start making the meeting minutes public some point soon as well. Additionally at some point when there are new contributors that want to make a solid, serious commitment to participate, we will have to include them in the ghangouts. Naturally, we just have to be careful that those meetings and minutes only concern the project and don't mingle in any confidential company information.

I am really excited about new contributors joining the Bokeh team, so thanks for bringing up questions like this so we can move forward including everyone!

Thanks,

Bryan

···

On Feb 19, 2015, at 11:55 AM, Sarah Bird <[email protected]> wrote:

Yes, have read the above, and was looking for something more specific.

I noticed today, for example, Bryan mentioned on a ticket "why not leave this for 0.8.2?" and Mateusz replied quickly "Just clicked 0.8.1 too eagerly." - to my reading this implies a whole level of understanding about a plan, that as an outside contributor, I don't have, and I don't get from the above links either.

Maybe you see it there and I'm just missing something in plain sight, in which case, I greatly appreciate your patience.

On Thu, Feb 19, 2015 at 9:47 AM, Damian Avila <[email protected]> wrote:
You probably need to take a look at:

1- http://bokeh.pydata.org/en/latest/docs/release_notes.html#roadmap

2- BEP 1: Issues and PRs management · bokeh/bokeh Wiki · GitHub

But we also probably need to make public code-freeze dates, estimated release dates, etc, at least after we effectively decide when it will be :wink:

On Thu, Feb 19, 2015 at 1:39 PM, Sarah Bird <[email protected]> wrote:
Hi all,

I'm wondering if I've missed a wiki page or a piece of documentation that outlines the timeframe for milestones.

The main place I would expect to see it is: Milestones - bokeh/bokeh · GitHub

I get the sense from comments on the issues that there is some shared understanding about timeframes amongst the core devs.

When thinking about PR I might like to do, it's really great to know what the schedule is looking like, and when the code freezes will be.

I know the project is moving really fast and sometimes there's a need for a quick release or things get delayed, so I don't have strong expectations that these things will be rigid, but some guidance would be useful.

Best,

Bird

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" 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/a/continuum.io/d/msgid/bokeh/3cfaf20b-0976-49eb-a535-a84afea41d50%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" 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/a/continuum.io/d/msgid/bokeh/CAM9Ly3EXe1R5WKaTH-Ud0K_E1c0cY%2BzLY2CacE1QL0hzhyPqmQ%40mail.gmail.com\.

For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" 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/a/continuum.io/d/msgid/bokeh/CA%2BEr%2BdQGoFCGZSWKPt3my2a%3D9wuROeh%2B446rWuakeB8mtVPKFw%40mail.gmail.com\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.