I would definitely prefer the separate -commits list for svn changes. No strong feelings about jira updates.
On Thu, Mar 12, 2009 at 10: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 >> >>> >> >> >
