Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

release 1.26.0 #173

Closed
tswast opened this issue Jul 17, 2020 · 4 comments
Closed

release 1.26.0 #173

tswast opened this issue Jul 17, 2020 · 4 comments
Assignees
@shollyman
Labels
api: bigquery Issues related to the googleapis/python-bigquery API. type: process A process-related concern. May include testing, release, or the like.

Comments

@tswast
Copy link
Contributor

tswast commented Jul 17, 2020

Any chance we could get a release? I'd like #170 in a released version to support a tool I'm building on my current team.
@product-auto-label product-auto-label bot added the api: bigquery Issues related to the googleapis/python-bigquery API. label Jul 17, 2020
@tswast tswast mentioned this issue Jul 17, 2020
Closed
2 tasks
@tswast
Copy link
Contributor Author

tswast commented Jul 17, 2020

Is #130 blocked on CI issues?

@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Jul 18, 2020
@plamut plamut added type: process A process-related concern. May include testing, release, or the like. and removed triage me I really want to be triaged. labels Jul 20, 2020
@plamut
Copy link
Contributor

plamut commented Jul 20, 2020

@tswast Samples checks have been added preemptively and will pass once #149 is done and merged.

I don't know the release schedule, but regularly releasing fixes makes sense to me. Perhaps we are waiting to also include a few PRs that are close to being done. @shollyman ?

@shollyman
Copy link
Contributor

It largely comes down to getting those samples moved over, which is still in flight. Do we want to gate the release on the samples changes?

Given we have clean separation of library and samples testing I'm okay with letting 1.26.0 get out with broken samples, but I don't know if anyone's expecting working sample targets as part of their own consumption. I have no problem releasing more frequently, so let's not wait on more than we need to.

@shollyman
Copy link
Contributor

Went ahead with the release in #130 to unblock the release while we finish sorting out the samples move.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shollyman shollyman

Labels
api: bigquery Issues related to the googleapis/python-bigquery API. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tswast @shollyman @plamut @yoshi-automation