Yes, user@ cannot reach new users, really. Twitter might, if we have enough
of adjacent followers to get it in front of the right people. On the other
hand, I find testimonials from experience convincing in this case.

Kenn

On Tue, Oct 23, 2018 at 2:59 PM Ahmet Altay <[email protected]> wrote:

>
>
> On Tue, Oct 23, 2018 at 9:16 AM, Thomas Weise <[email protected]> wrote:
>
>>
>>
>> On Mon, Oct 22, 2018 at 2:42 PM Ahmet Altay <[email protected]> wrote:
>>
>>> We attempted to collect feedback on the mailing lists but did not get
>>> much input. From my experience (mostly based on dataflow) there is a
>>> sizeable group of users who are less interested in new features and want a
>>> version that is stable, that does not have security issues, major data
>>> integrity issues etc. In Beam's existing release model that corresponds to
>>> the latest release.
>>>
>>> It would help a lot if we can hear the perspectives of other users who
>>> are not present here through the developers who work with them.
>>>
>>
>> Perhaps user@ and Twitter are good ways to reach relevant audience.
>>
>
> We tried user@ before did not get any feedback [1]. Polling on twitter
> sounds like a good idea. Unless there is an objection, I can start a poll
> with Thomas's proposed text as is on Beam's twitter account.
>
> [1]
> https://lists.apache.org/thread.html/7d890d6ed221c722a95d9c773583450767b79ee0c0c78f48a56c7eba@%3Cuser.beam.apache.org%3E
>
>
>>
>> A poll could look like this:
>>
>> The Beam community is considering LTS (Long Term Support) for selected
>> releases. LTS releases would only contain critical bug fixes (security,
>> data integrity etc.) and offer an alternative to upgrading to latest Beam
>> release with new features. Please indicate your preference for Beam
>> upgrades:
>>
>> 1) Always upgrading to the latest release because I need latest features
>> along with bug fixes
>> 2) Interested to switch to LTS releases to obtain critical fixes
>> 3) Not upgrading (using older release for other reasons)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>

Reply via email to