We're gonna have to do that anyway, and I believe the process is automated. So why wait?
On 14 March 2013 14:26, Chip Childers <chip.child...@sungard.com> wrote: > On Thu, Mar 14, 2013 at 10:24:13AM -0400, David Nalley wrote: > > On Thu, Mar 14, 2013 at 10:22 AM, Noah Slater <nsla...@apache.org> > wrote: > > > Dear community, > > > > > > I would like to establish the cloudstack-announce mailing list. > > > > > > The primary purpose of this mailing list will be to post release > > > announcements to. > > > > > > It is important that we provide high signal channels through which > people > > > can discover project status. > > > > > > I have two use cases in mind. Firstly, the user who is not interested > in > > > participating on the mailing lists, and just wants to know about new > > > releases. Secondly, a downstream packager, or third party, that needs > to > > > put their own release machinery into gear. > > > > > > If nobody objects in 72 hours, I will assume lazy consensus and > establish > > > the list. > > > > > > Thanks, > > > > > > -- > > > NS > > > > +1 - release and security announcements certainly need a low volume > channel. > > > > Happy to be a mod on that list if you need additional. > > > > --David > > > > +1 - However I would suggest that we may want to hold off on actually > creating the list right now. Since we are going through the graduation > process, we'll end up having to move from @i.a.o to @cloudstack.a.o for > our list addresses as part of the transition. Do you think waiting > might make sense here? > -- NS
