Milestones for 2015?

[jgeewax]

Hi guys,

Now that 2015 is here, I was wondering if we could take another pass at the milestones. We originally went with "let's just try to break this down by different services" and that seemed to kick things off. I don't know if that's the same right now, given we have the majority of work done for the different services, and still have some finishing touches.

Could we brainstorm some good milestones for the year and then update them in here?

Straw man for us to discuss

• gcloud.datastore 1.0 (any issue related to Datastore getting to 1.0 from now on would go here)
• NDB Integrated into Datastore (I suspect there will be a lot of issues related to this -- maybe this is a sub-milestone to the above?)
• gcloud.storage 1.0 (include getting Google's Cloud Storage team to give us a 👍 on this)
• Documentation 1.0 (anything that's needed to get our docs being what we consider to be 1.0 "done")
• gcloud.pubsub 0.1 (anything that we need to do to get pubsub to an "alpha" that works but might be backwards incompatible over time)
• gcloud.pubsub 0.5 (get to "beta" -- works, stable, less likely to be backwards incompatible, but still useful)
• gcloud.pubsub 1.0 (including sign-off from Google's Cloud Pub/Sub team)

(same for DNS, BigQuery, SQL, and Compute)

Thoughts?

Straw man of service priorities

1. Datastore
2. Storage
3. Pub/Sub
4. DNS
5. BigQuery
6. SQL
7. Compute

Proposed "milestones" to add to gcloud-python for our 2015 work

1. datastore stable
2. datastore future
3. storage stable
4. storage future
5. pubsub alpha
6. pubsub beta
7. pubsub stable
8. pubsub future
9. dns alpha
10. dns beta
11. dns stable
12. dns future

and a "catch all" called "stable" for things that aren't specific to a service.

/cc @dhermes @tseaver

[dhermes]

I like it. We'll likely need to prioritize PubSub / DNS / BigQuery / SQL / Compute. I'm not clear which order you prefer.

[jgeewax]

Cool - @dhermes Updated the comment with a straw-man of priorities.

[jgeewax]

Any more suggestions before we put this to a vote?

[tseaver]

Is the following a typo:

gcloud.pubsub 1.0 (including sign-off from Google's Cloud DNS team)

I would expect the sign-off would be from the Pubsub team?

[tseaver]

Also, is adding gcloud.datastore.ndb a blocker for a datastore 1.0 milestone?

[jgeewax]

@tseaver

• Yes it's a type, I'll fix that.
• I don't think NDB is a blocker, I think we're targeting somewhere in Q2 (Q1 if we're extra aggressive)

[jennolsen84]

python3 👍. See a lot of great from @tseaver work towards that

Also perhaps something related to GKE/Kubernetes?

[jgeewax]

Hi guys,

Just updated the issue with a proposal of the milestones to create. Can we get some +1's or any further revisions ?
/cc @tseaver @dhermes

[tseaver]

@jgeewax I'm not sure what the -future bits mean WRT the other priorities. Other than that, LGTM.

[jgeewax]

"future" is stuff that aren't blocking a stable release, but are things we want to do later. Think we should drop them ?

[dhermes]

SGTM

[jgeewax]

OK - these are all created. I spent a bit of time moving issues around -- hopefully we're close enough.

When in doubt, put stuff in the "stable" milestone, and we can push it out to "future" if we decide it's not a blocker for the stable release for a service.