You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Johan Oskarsson <jo...@oskarsson.nu> on 2009/03/11 19:19:17 UTC
Jira to dev list emails
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
Re: Jira to dev list emails
Posted by Prashant Malik <pm...@gmail.com>.
I have found the Jira discussions for most of the products to be very useful
so I would agree with that.
- Prashant
On 3/12/09, Ian Holsman <ia...@holsman.net> wrote:
>
> 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-user@googlegroups.com (Cassandra's legacy Google group).
>>
>> Just to be clear:
>>
>> Subjects that go to the cassandra-commits@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-subscribe@incubator.apache.org
>>
>>
>> If you also want to receive SVN commits and jira bug/task tracking
>> subscribe
>> by sending an email to:
>>
>> cassandra-commits-subscribe@incubator.apache.org
>>
>> Donald
>> -----Original Message-----
>> From: Avinash Lakshman [mailto:avinash.lakshman@gmail.com]
>> Sent: Thursday, 12 March 2009 4:57 PM
>> To: cassandra-dev@incubator.apache.org; matthieu.riou@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
>> <ma...@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-commits@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 <tc...@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
> Ian@Holsman.net
>
>
>
>
Re: Jira to dev list emails
Posted by Ian Holsman <ia...@holsman.net>.
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-user@googlegroups.com (Cassandra's legacy Google
> group).
>
> Just to be clear:
>
> Subjects that go to the cassandra-commits@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-subscribe@incubator.apache.org
>
>
> If you also want to receive SVN commits and jira bug/task tracking
> subscribe
> by sending an email to:
>
> cassandra-commits-subscribe@incubator.apache.org
>
> Donald
> -----Original Message-----
> From: Avinash Lakshman [mailto:avinash.lakshman@gmail.com]
> Sent: Thursday, 12 March 2009 4:57 PM
> To: cassandra-dev@incubator.apache.org; matthieu.riou@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
> <ma...@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-commits@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 <tc...@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
Ian@Holsman.net
RE: Jira to dev list emails
Posted by Donald Casson <do...@gmail.com>.
Adding cassandra-user@googlegroups.com (Cassandra's legacy Google group).
Just to be clear:
Subjects that go to the cassandra-commits@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-subscribe@incubator.apache.org
If you also want to receive SVN commits and jira bug/task tracking subscribe
by sending an email to:
cassandra-commits-subscribe@incubator.apache.org
Donald
-----Original Message-----
From: Avinash Lakshman [mailto:avinash.lakshman@gmail.com]
Sent: Thursday, 12 March 2009 4:57 PM
To: cassandra-dev@incubator.apache.org; matthieu.riou@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
<ma...@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-commits@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 <tc...@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
> > >>>
> >
> >
>
Re: Jira to dev list emails
Posted by Avinash Lakshman <av...@gmail.com>.
Keep the commits separate.
Avinash
On Thu, Mar 12, 2009 at 9:52 AM, Matthieu Riou <ma...@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-commits@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 <tc...@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
> > >>>
> >
> >
>
Re: Jira to dev list emails
Posted by Jonathan Ellis <jb...@gmail.com>.
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 <ma...@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-commits@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 <tc...@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
>> >>>
>>
>>
>
Re: Jira to dev list emails
Posted by Matthieu Riou <ma...@gmail.com>.
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-commits@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 <tc...@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
> >>>
>
>
Re: Jira to dev list emails
Posted by Johan Oskarsson <jo...@oskarsson.nu>.
Who would have the permissions needed to enable this? One of the
committers or a mentor?
/Johan
Sandeep Tata wrote:
> I agree.
>
> On Wed, Mar 11, 2009 at 3:11 PM, Torsten Curdt <tc...@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
>>>
Re: Jira to dev list emails
Posted by Sandeep Tata <sa...@gmail.com>.
I agree.
On Wed, Mar 11, 2009 at 3:11 PM, Torsten Curdt <tc...@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
>>
>
Re: Jira to dev list emails
Posted by Torsten Curdt <tc...@apache.org>.
+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
>