@mziccard I want to get your opinion on a good workflow for this issue. I think there are a couple options:

Create a branch off GoogleCloudPlatform/gcloud-java/master (like the update-datastore branch) and merge in incremental PRs.
Create a branch like in Generate Javadocs and put them in the gh-pages branch? #1 but only have one big PR. Rebase the branch onto master to keep it up to date.
Merge commits into master, but comment on the readme saying "do not use, currently under development".

@aozarov suggests #1 because incremental PRs are much easier to review and also because people using the library won't mistakenly think the Resource Manager library is ready. I agree with those points, but there's a downside that we can't rebase work to make the history clean. (Suppose there's a situation like in with the update-datastore branch in #277, where some of my PRs have been merged into master. Then any PR with a rebase will cause a merge conflict because my commits already upstream will have different commit hashes). I vote option 1 because option 2 seems impractical for the reviewer and option 3 could be confusing to users. What's your opinion/what do you plan to do for BigQuery?

Figure out the work needed for Resource Manager service #297

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions