Yes. The submitted jira-INFRA is:
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-12475
Thanks for Henry's proposal.
2016-08-24 3:33 GMT+08:00 Jean-Baptiste Onofré :
> Hi Henry,
>
> I already requested the issues@ mailing list creation and Liang submitted
Hi Henry,
I already requested the issues@ mailing list creation and Liang
submitted a Jira to INFRA.
Regards
JB
On 08/23/2016 07:27 PM, Henry Saputra wrote:
Ok, if no objection I will ask INFRA to help makes the notification change
for option 2 plus new list issues@
Thanks!
On Fri, Aug
Ok, if no objection I will ask INFRA to help makes the notification change
for option 2 plus new list issues@
Thanks!
On Fri, Aug 19, 2016 at 7:57 PM, praveen adlakha
wrote:
> +1 for option 2.
>
> On Aug 20, 2016 8:22 AM, "Ravindra Pesala"
+1 for option 2.
On Aug 20, 2016 8:22 AM, "Ravindra Pesala" wrote:
> +1 for option 2 (Henry proposed solution).
>
> Thanks,
> Ravi.
>
> On Sat, 20 Aug 2016 7:54 am chenliang613, wrote:
>
> > Agree for modified Option2 which be proposed by Henry.
+1 for option 2 (Henry proposed solution).
Thanks,
Ravi.
On Sat, 20 Aug 2016 7:54 am chenliang613, wrote:
> Agree for modified Option2 which be proposed by Henry.
> We will implement it as per the solution.
>
> Thanks for all of you participated in discussion and vote.
Agree for modified Option2 which be proposed by Henry.
We will implement it as per the solution.
Thanks for all of you participated in discussion and vote.
Regards
Liang
--
View this message in context:
Hi Henry,
Agreed.
it's what we are using in Apache Karaf, Beam, Flink, ...
I think it's very convenient.
Regards
JB
On 08/18/2016 08:43 PM, Henry Saputra wrote:
How about modification of Option 2:
Issue Created, send mails to dev@carbondata.incubator.apache.org
Issue Created and all other
+1 for option 2
On Aug 19, 2016 6:36 AM, "chenliang613" wrote:
> Hi
>
> I agree Henry's proposal.
>
> Issue Created, send mails to dev@mailing list
> Issue Created and all other JIRA events send mails to new mailing list at
> issues@mailing list.
>
>
> Regards
> Liang
>
Hi
I agree Henry's proposal.
Issue Created, send mails to dev@mailing list
Issue Created and all other JIRA events send mails to new mailing list at
issues@mailing list.
Regards
Liang
--
View this message in context:
Option2:+1
在 2016/8/18 15:57, Liang Big data 写道:
Hi all
Please discuss and vote, do you think what kind of JIRA issue events need
send mails to dev@carbondata.incubator.apache.org?
Option1: None, all JIRA issue events don't need send any mails to
dev@carbondata.incubator.apache.org, users
Hi Henry,
This change sounds good to me.
Make sense to have issues@. Lot of other projects have that as well.
+1 for option 2, considering above changes
Regards,
Uma
On Thu, Aug 18, 2016 at 11:43 AM, Henry Saputra
wrote:
> How about modification of Option 2:
>
>
How about modification of Option 2:
Issue Created, send mails to dev@carbondata.incubator.apache.org
Issue Created and all other JIRA events send mails to new mailing list at
iss...@carbondata.incubator.apache.org
- Henry
On Thu, Aug 18, 2016 at 12:57 AM, Liang Big data
Option2, better add Issue closed event
--
View this message in context:
http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/Open-discussion-and-Vote-What-kind-of-JIRA-issue-events-need-send-mail-to-dev-carbondata-incubator-ag-tp321p325.html
Sent from the Apache CarbonData
Any of this is fine with me.
Option 2.1: Issue Created and Issue Commented,+ issue resolved.
+ stop PR comment updating Jira comment.
Option 4: Send them to another mailing list dev-notification
On Thu, Aug 18, 2016 at 2:12 PM, Ravindra Pesala
wrote:
> +1
14 matches
Mail list logo