my preference would be that the jira's go to the dev group, as is the
case with most of the lucene projects & hadoop projects.
ALOT of discussion happens inside the jira's, and it's useful for
people to see that.
--I
On 13/03/2009, at 10:16 AM, Donald Casson wrote:
Adding cassandra-u...@googlegroups.com (Cassandra's legacy Google
group).
Just to be clear:
Subjects that go to the cassandra-comm...@incubator.apache.org :
SVN Comit's
Jira Bug/task tracking
Things that go to the cassandra-dev@incubator.apache.org :
General discussion about Cassandra development/use case/support
discussions
I think it's best to keep server generated email's (Jira and SVN) to a
separate list and developer/use case/support discussions to its own
list.
If you want access to both then subscribe to both.
If you want to only subscribe to the dev discussion mailing list then
subscribe by sending an email to:
cassandra-dev-subscr...@incubator.apache.org
If you also want to receive SVN commits and jira bug/task tracking
subscribe
by sending an email to:
cassandra-commits-subscr...@incubator.apache.org
Donald
-----Original Message-----
From: Avinash Lakshman [mailto:avinash.laksh...@gmail.com]
Sent: Thursday, 12 March 2009 4:57 PM
To: cassandra-dev@incubator.apache.org; matthieu.r...@gmail.com
Subject: Re: Jira to dev list emails
Keep the commits separate.
Avinash
On Thu, Mar 12, 2009 at 9:52 AM, Matthieu Riou
<matthieu.r...@gmail.com>wrote:
On Thu, Mar 12, 2009 at 3:05 AM, Johan Oskarsson <jo...@oskarsson.nu>
wrote:
Who would have the permissions needed to enable this? One of the
committers or a mentor?
Right now everything is setup to go to
cassandra-comm...@incubator.apache.org. You can subscribe and
you'll get
the
commit notifications from Subversion as well. I could change Jira
to use
cassandra-dev but that sometimes create a lot of overhead for
casual devs.
So what's the consensus? Keep cassandra-commits or change to
cassandra-dev?
Matthieu
/Johan
Sandeep Tata wrote:
I agree.
On Wed, Mar 11, 2009 at 3:11 PM, Torsten Curdt <tcu...@apache.org>
wrote:
+1
On Wed, Mar 11, 2009 at 19:19, Johan Oskarsson
<jo...@oskarsson.nu>
wrote:
I would suggest setting it up so that any changes to jira
issues are
also sent to the dev mailinglist.
This way a lot more eyes will see the progress of the development
work
that would otherwise be hidden in jira. It would create a
positive
feedback loop of more comments on issues etc.
Thoughts on this? Who would have permissions to enable it?
/Johan
--
Ian Holsman
i...@holsman.net
