[openstack-dev] OpenStack-Announce List

Andreas Jaeger aj at suse.com
Thu Jan 14 07:22:52 UTC 2016


On 2016-01-14 08:13, Tom Fifield wrote:
> So, I'm prompted by another 20 oslo release emails to dredge up this
> thread :)
>
> There appears to be broad consensus that those shouldn't be going to the
> announce list ... what do we need to do to get that to change to posted
> to "-dev + batched inside the weekly -dev digest from thingee" as
> Thierry suggested?

So, those 20 odd olso release emails all went to -dev, the release team 
changed the logic, see also 
http://lists.openstack.org/pipermail/openstack-dev/2016-January/083749.html

Not sure about the "Batching inside the weekly digest from thingee",

Andreas

>
>
> Regards,
>
>
> Tom
>
> On 14/12/15 17:12, Tom Fifield wrote:
>> ... and back to this thread after a few weeks :)
>>
>> The conclusions I saw were:
>> * Audience for openstack-announce should be "users/non-dev"
>> * Service project releases announcements are good
>> * Client library release announcements good
>> * Security announcements are good
>> * Internal library (particularly oslo) release announcements don't fit
>>
>> Open Questions:
>> * Where do Internal library release announcements go? [-dev or new
>> -release list or batched inside the weekly newsletter]
>> * Do SDK releases fit on -announce?
>>
>>
>> Regards,
>>
>>
>> Tom
>>
>>
>> On 20/11/15 12:00, Tom Fifield wrote:
>>> Hi all,
>>>
>>> I'd like to get your thoughts about the OpenStack-Announce list.
>>>
>>> We describe the list as:
>>>
>>> """
>>> Subscribe to this list to receive important announcements from the
>>> OpenStack Release Team and OpenStack Security Team.
>>>
>>> This is a low-traffic, read-only list.
>>> """
>>>
>>> Up until July 2015, it was used for the following:
>>> * Community Weekly Newsletter
>>> * Stable branch release notifications
>>> * Major (i.e. Six-monthly) release notifications
>>> * Important security advisories
>>>
>>> and had on average 5-10 messages per month.
>>>
>>> After July 2015, the following was added:
>>> * Release notifications for clients and libraries (one email per
>>> library, includes contributor-focused projects)
>>>
>>> resulting in an average of 70-80 messages per month.
>>>
>>>
>>> Personally, I no longer consider this volume "low traffic" :)
>>>
>>> In addition, I have been recently receiving feedback that users have
>>> been unsubscribing from or deleting without reading the list's posts.
>>>
>>> That isn't good news, given this is supposed to be the place where we
>>> can make very important announcements and have them read.
>>>
>>> One simple suggestion might be to batch the week's client/library
>>> release notifications into a single email. Another might be to look at
>>> the audience for the list, what kind of notifications they want, and
>>> chose the announcements differently.
>>>
>>> What do you think we should do to ensure the announce list remains
>>> useful?
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>> Tom
>>>
>>> __________________________________________________________________________
>>>
>>>
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> __________________________________________________________________________
>>
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
        HRB 21284 (AG Nürnberg)
     GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126




More information about the OpenStack-dev mailing list