Hi,
There are other Apache projects that have a separate list for JIRA issue. For
example:
http://cloudstack.apache.org/mailing-lists.html
http://hadoop.apache.org/mailing_lists.html
And there's probably others.
Thanks,
Justin
It's going to make filtering the emails a lot easier now... gmail does a
poor job compared to my outlook.
-Mark
On Tue, May 28, 2013 at 3:24 PM, Erik de Bruin wrote:
> Agreed. Committers are committing, so they want to track the issues
> they work on anyways, I'm sure. If they hate being kept
You should allow a lot longer than 30 minutes before calling a vote.
Like maybe 72 hours.
Regards,
Dave
On May 28, 2013, at 11:56 AM, Erik de Bruin wrote:
> Let's vote!
>
> EdB
>
>
>
> On Tue, May 28, 2013 at 8:51 PM, Alex Harui wrote:
>> Vote is required according to [1]
>>
>> [1] http:/
A standard action would be to create commits@ and issues@ MLs and move both git
commits and JIRA issues off of the dev list.
Some of the PMC will need to subscribe to these and pay attention to the
changing codebase.
Regards,
Dave
On May 28, 2013, at 11:32 AM, OmPrakash Muppirala wrote:
> Oka
On Tue, May 28, 2013 at 5:11 PM, Justin Mclean wrote:
> Hi,
>
> I know I'm probably responsible for the majority of JIRA traffic. I'm not
> opposed to having all JIRA emails go to a new list but there a few things
> we should think about.
>
> Currently the JIRA messages are very easy to filter out
Hi,
I know I'm probably responsible for the majority of JIRA traffic. I'm not
opposed to having all JIRA emails go to a new list but there a few things we
should think about.
Currently the JIRA messages are very easy to filter out so moving them to
another list is really no different to an ema
Agreed. Committers are committing, so they want to track the issues
they work on anyways, I'm sure. If they hate being kept up to date so
much, they can always unsubscribe. This is not a big thing, it's just
a mailing list.
EdB
On Tue, May 28, 2013 at 8:58 PM, OmPrakash Muppirala
wrote:
> On T
On Tue, May 28, 2013 at 11:54 AM, Nicholas Kwiatkowski wrote:
> I don't think we need to auto-add committers... Let them add themselves,
> incase they either don't want the notices (and view them via RSS direct
> from JIRA), or they want to use another email address. It should be a
> public list
Let's vote!
EdB
On Tue, May 28, 2013 at 8:51 PM, Alex Harui wrote:
> Vote is required according to [1]
>
> [1] http://www.apache.org/dev/committers.html#new-mailing-list
>
> On 5/28/13 11:45 AM, "Erik de Bruin" wrote:
>
>>Shouldn't everyone be able to subscribe? Or are you saying that but
>>d
I don't think we need to auto-add committers... Let them add themselves,
incase they either don't want the notices (and view them via RSS direct
from JIRA), or they want to use another email address. It should be a
public list so anybody could join if they want.
-Nick
On Tue, May 28, 2013 at 2:
Vote is required according to [1]
[1] http://www.apache.org/dev/committers.html#new-mailing-list
On 5/28/13 11:45 AM, "Erik de Bruin" wrote:
>Shouldn't everyone be able to subscribe? Or are you saying that but
>did I miss it... ;-)
>
>EdB
>
>On Tue, May 28, 2013 at 8:32 PM, OmPrakash Muppirala
Yes everyone should be able to subscribe, I thought that was obvious :-) I
doubt if regular folks would subscribe to that list though.
The cool thing about JIRA is if you log in and comment on a JIRA issue, it
will automatically add you as a 'watcher' and will send you notifications
for further a
Shouldn't everyone be able to subscribe? Or are you saying that but
did I miss it... ;-)
EdB
On Tue, May 28, 2013 at 8:32 PM, OmPrakash Muppirala
wrote:
> Okay, moving to a new thread.
>
> Do we need a vote for this or is there sufficient consensus in the
> community?
>
> We dont want to lose pe
Okay, moving to a new thread.
Do we need a vote for this or is there sufficient consensus in the
community?
We dont want to lose people because of all the spam that gets generated by
the JIRA emails. That should be a big priority for us.
The proposal is:
1. Create a list: j...@flex.apache.org
14 matches
Mail list logo
