On 13:04 Feb 27, Clint Byrum wrote:
> Excerpts from Doug Hellmann's message of 2017-02-27 15:43:12 -0500:
> > 
> > As a person who sends a lot of process-driven email to this list,
> > it is not working for my needs to communicate with others.
> > 
> > Over the past few cycles when I was the release PTL, I always had
> > a couple of PTLs say there was too much email on this list for them
> > to read, and that they had not read my instructions for managing
> > releases. That resulted in us having to train folks at the last
> > minute, remind them of deadlines, deal with them missing deadlines,
> > and otherwise increased the release team's workload.
> > 
> > It is possible the situation will improve now that the automation
> > work is mostly complete and we expect to see fewer significant
> > changes in the release workflow. That still leaves quite a few
> > people regularly surprised by deadlines, though.
> > 
> 
> The problem above is really the krux of it. Whether or not you can keep
> up with the mailing list can be an unknown, unknown. Even now, those
> who can't actually handle the mailing list traffic are in fact likely
> missing this thread about whether or not people can handle the mailing
> list traffic (credit fungi for pointing out this irony to me on IRC).

I feel like this subject comes up in different forms.

FWIW, the dev digest does cover information like release deadlines, elections,
etc. Here's an example:

https://www.openstack.org/blog/2017/01/openstack-developer-mailing-list-digest-20170120/

For anyone that feels like the current ML system is not working and you're
missing important information, do yourself a favor and at least double check
the digest. Suggestions are welcome!


-- 
Mike Perez

Attachment: pgpPPZaNst4PF.pgp
Description: PGP signature

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to