Releasing new vendored artifacts won't generally imply a full Beam release. The plan is to pick up the new artifact version at HEAD which will roll into the next release.
For this particularly case, the question is if the Dataflow issue that this fixes (BEAM-6056) warrants a hotfix release (2.9.1). I don't know the answer-- Ahmet/Kenn do you have any thoughts?
Does this imply that we need a subsequent full release afterwards?
I am assuming this new release is related to the reported issues with
the dataflow worker or is this something different?
On Thu, Dec 20, 2018 at 2:51 AM Kenneth Knowles <kenn@xxxxxxxxxx> wrote:
> - sigs good
> - `jar tf` looks good
> On Wed, Dec 19, 2018 at 7:54 PM Scott Wegner <swegner@xxxxxxxxxx> wrote:
>> Please review and vote on the release candidate #1 for the vendored artifact gRPC 1.13.1 v0.2
>> [ ] +1, Approve the release
>> [ ] -1, Do not approve the release (please provide specific comments)
>> This is a follow-up to the previous thread about vendoring updates 
>> The complete staging area is available for your review, which includes:
>> * all artifacts to be deployed to the Maven Central Repository ,
>> * commit hash "3b8abca3ca3352e6bf20e059f17324049a2eae0a" ,
>> * artifacts which are signed with the key with fingerprint
>> 5F47BD54C52008007288FF4D3593BA6C25ABF71F 
>> The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes.
>>  https://lists.apache.org/thread.html/9a55d12000cb3b1b61620b7dc4009d1351e6b8c70951f70aeb358583@%3Cdev.beam.apache.org%3E
>>  https://repository.apache.org/content/repositories/orgapachebeam-1055/
>>  https://github.com/apache/beam/pull/7328
>>  https://dist.apache.org/repos/dist/release/beam/KEYS
>> Got feedback? tinyurl.com/swegner-feedback