Re: 2.7.0 release notes inconsistent with released code

Thanks Andrew - and sorry folks, that was simply me doing a bad email search as I looked into the issue. I don't think there is much more to do communicate. I just corrected the label in Jira and I see the release notes are updated automatically - I'm not sure how we can include a note to say that

Re: 2.7.0 release notes inconsistent with released code

As I understand, Tim's concern is the accuracy of the release notes, and +1 for correcting them. In the end it does not matter that much to the users when a release was proposed to be cut vs. when it actually happened, but what they get with the release. Perhaps between the contributors we could g

Re: 2.7.0 release notes inconsistent with released code

Keep reading the proposal thread and you'll find: "We should follow the calendar and aim to cut on 8/29, not 9/7 as I incorrectly wrote earlier." There were several folowup emails in the thread with reminders of the release cut date. Is there something we should do to better communicate release cut

Re: 2.7.0 release notes inconsistent with released code

On Mon, Oct 8, 2018 at 3:17 AM Tim Robertson wrote: > > Do we correct release notes when mistakes are spotted? > I think we should, yes. Release notes are long-lived documents that should be accurate. The correction should be mentioned in the notes so that anyone who previously read the incorrec

2.7.0 release notes inconsistent with released code

Hi folks Our release notes [1] for 2.7.0 say that Beam supports Elasticsearch 6 ( BEAM-5107 ). The 2.7.0 code [2] however does not seem to, while master does [3]. The PR [4] was merged on the 6th September and in the 2.7.0 chat I see that Charles an