You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release 'api_core-1.6.0a2'? or 'api_core-1.5.1'? #6326
@tswast I believe @lukesneeringer is the one who can answer your question about PR #6267 and the api_core-1.6.0a1 release.
My take: given that we follow the "keep master releasable at all times" development practice, I believe that we should move the changes from #6267 off onto a branch (or even just revert it and re-merge later) to allow for making an api_core-1.5.1 release from master, including your bugfix from #6310.
As an alternative, we could make an api_core-1.5-maint branch from 7527a4e (the last commit on master touching api_core/ before #6267), and cherry pick e368317 into it from #6310 in order to make the api_core-1.5.1 release you need.
Activity
tseaver commentedon Oct 29, 2018
@tswast I believe @lukesneeringer is the one who can answer your question about PR #6267 and the
api_core-1.6.0a1release.My take: given that we follow the "keep
masterreleasable at all times" development practice, I believe that we should move the changes from #6267 off onto a branch (or even just revert it and re-merge later) to allow for making anapi_core-1.5.1release from master, including your bugfix from #6310.As an alternative, we could make an
api_core-1.5-maintbranch from 7527a4e (the last commit onmastertouchingapi_core/before #6267), and cherry pick e368317 into it from #6310 in order to make theapi_core-1.5.1release you need.[-]Release api_core 1.6.0a2[/-][+]Release 'api_core-1.6.0a2'? or 'api_core-1.5.1'?[/+]Don't URL-encode slashes in gRPC request headers. (#6310)
Back out changes from #6267 / 'api_core-1.6.0a1' release. (#6328)
Back out changes from #6267 / 'api_core-1.6.0a1' release. (#6328)