Shall we merge the dev mailing lists? This should reduce the cross-posting and
can be completely automated (other than you may have to update your client-side
filters) and was part of the plan to merge dev efforts.
I'd propose it be called lucene-solr-...@l.a.o. I can put in an issue for
infr
why not just "d...@lucene.apache.org"?
On Mon, Mar 22, 2010 at 11:44 AM, Grant Ingersoll wrote:
> Shall we merge the dev mailing lists? This should reduce the cross-posting
> and can be completely automated (other than you may have to update your
> client-side filters) and was part of the pl
Logistically, how would this work?
would d...@lucene.apache.org be an alias for java-dev and solr-dev? or
a whole new list?
Would people need to subscribe to it, or would you already be on the
list if you were on java/solr dev? If we are on both lists, do we get
two copies of every message?
On
On Mar 22, 2010, at 12:43 PM, Ryan McKinley wrote:
> Logistically, how would this work?
>
> would d...@lucene.apache.org be an alias for java-dev and solr-dev? or
> a whole new list?
I thought of d...@l.a.o, but we still have other dev lists under the PMC, so
didn't want to imply it was the on
https://issues.apache.org/jira/browse/INFRA-2567
On Mar 22, 2010, at 11:44 AM, Grant Ingersoll wrote:
> Shall we merge the dev mailing lists? This should reduce the cross-posting
> and can be completely automated (other than you may have to update your
> client-side filters) and was part of th
