Thank you very much!
Am 04.03.2019 um 18:25 schrieb Marcelo Vanzin:
FYI, it should all be done now, so if you want to get notifications,
either sign up to issues@, or watch the repo on github.
On Fri, Feb 22, 2019 at 9:49 AM Marcelo Vanzin wrote:
Jira link:
Many thanks.
> On Mar 4, 2019, at 12:25 PM, Marcelo Vanzin
> wrote:
>
> FYI, it should all be done now, so if you want to get notifications,
> either sign up to issues@, or watch the repo on github.
>
> On Fri, Feb 22, 2019 at 9:49 AM Marcelo Vanzin wrote:
>>
>> Jira link:
FYI, it should all be done now, so if you want to get notifications,
either sign up to issues@, or watch the repo on github.
On Fri, Feb 22, 2019 at 9:49 AM Marcelo Vanzin wrote:
>
> Jira link: https://issues.apache.org/jira/browse/INFRA-17892
>
> On Fri, Feb 22, 2019 at 9:44 AM Marcelo Vanzin
Thank you very much for taking care of this!
Am 22.02.2019 um 18:49 schrieb Marcelo Vanzin:
Jira link: https://issues.apache.org/jira/browse/INFRA-17892
On Fri, Feb 22, 2019 at 9:44 AM Marcelo Vanzin wrote:
Thanks all, vote passes with 11 +1s, no -1s.
I'll file the INFRA ticket and link it
Jira link: https://issues.apache.org/jira/browse/INFRA-17892
On Fri, Feb 22, 2019 at 9:44 AM Marcelo Vanzin wrote:
>
> Thanks all, vote passes with 11 +1s, no -1s.
>
> I'll file the INFRA ticket and link it back here soon.
>
> On Tue, Feb 19, 2019 at 1:35 PM Marcelo Vanzin wrote:
> >
> > I'm
Thanks all, vote passes with 11 +1s, no -1s.
I'll file the INFRA ticket and link it back here soon.
On Tue, Feb 19, 2019 at 1:35 PM Marcelo Vanzin wrote:
>
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
>
> -
+1
Oliver
Am 19.02.19 um 22:35 schrieb Marcelo Vanzin:
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
>
> - +1 to redirect github updates of all commons repos to the issues@ list
> - -1 to keep things as is
>
On Wed, Feb 20, 2019 at 11:13 AM Pascal Schumacher
wrote:
> Am 20.02.2019 um 19:39 schrieb Marcelo Vanzin:
> > Rob:
> >> I almost think that we should have Pull Requests generate jiras.
> > I've seen this set up in a couple of projects and jira becomes
> > unreadable... the updates generated by
Am 20.02.2019 um 19:39 schrieb Marcelo Vanzin:
Rob:
I almost think that we should have Pull Requests generate jiras.
I've seen this set up in a couple of projects and jira becomes
unreadable... the updates generated by github are horrible to read. I
really don't like them.
Imho the way to
On Wed, Feb 20, 2019 at 5:41 AM Gary Gregory wrote:
> Is this a LAZY VOTE?
Sorry, but not familiar with the semantics of when to call a lazy vs.
non-lazy vote. Given the current number of votes, does it matter?
Rob:
> I almost think that we should have Pull Requests generate jiras.
I've seen
+1
On Wed, 20 Feb 2019, 3:05 am Marcelo Vanzin,
wrote:
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
>
> - +1 to redirect github updates of all commons repos to the issues@ list
> - -1 to keep things as is
>
>
+1
On February 20, 2019 at 08:41:15, Gary Gregory (garydgreg...@gmail.com)
wrote:
Is this a LAZY VOTE?
Gary
On Wed, Feb 20, 2019 at 7:36 AM Rob Tompkins wrote:
> +1
>
> (Note. We still need to have the github messages either land on an email
> list or generate jira’s for traceability. I
Is this a LAZY VOTE?
Gary
On Wed, Feb 20, 2019 at 7:36 AM Rob Tompkins wrote:
> +1
>
> (Note. We still need to have the github messages either land on an email
> list or generate jira’s for traceability. I almost think that we should
> have Pull Requests generate jiras.)
>
> > On Feb 19, 2019,
+1
(Note. We still need to have the github messages either land on an email list
or generate jira’s for traceability. I almost think that we should have Pull
Requests generate jiras.)
> On Feb 19, 2019, at 4:35 PM, Marcelo Vanzin
> wrote:
>
> I'm opening a vote based on recent discussions
+1
Am Di., 19. Feb. 2019 um 22:35 Uhr schrieb Marcelo Vanzin
:
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
>
> - +1 to redirect github updates of all commons repos to the issues@ list
> - -1 to keep things as
(please make sure to add me to CC)
+1
On Tue, 19 Feb 2019 at 21:13, Stefan Bodewig wrote:
>
> On 2019-02-19, Marcelo Vanzin wrote:
>
> > I'm opening a vote based on recent discussions about the extra noise
> > generated by github updates going to dev@. So please vote:
>
> > - +1 to redirect
On 2019-02-19, Marcelo Vanzin wrote:
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
> - +1 to redirect github updates of all commons repos to the issues@ list
> - -1 to keep things as is
> If the vote passes,
Le mar. 19 févr. 2019 à 22:35, Marcelo Vanzin
a écrit :
>
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
>
> - +1 to redirect github updates of all commons repos to the issues@ list
> - -1 to keep things as is
+1
Am 19.02.2019 um 22:35 schrieb Marcelo Vanzin:
I'm opening a vote based on recent discussions about the extra noise
generated by github updates going to dev@. So please vote:
- +1 to redirect github updates of all commons repos to the issues@ list
- -1 to keep things as is
If the vote
+1
On Tue, Feb 19, 2019 at 1:35 PM Marcelo Vanzin
wrote:
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
>
> - +1 to redirect github updates of all commons repos to the issues@ list
> - -1 to keep things as is
>
I'm opening a vote based on recent discussions about the extra noise
generated by github updates going to dev@. So please vote:
- +1 to redirect github updates of all commons repos to the issues@ list
- -1 to keep things as is
If the vote passes, I'll take care of opening an infra ticket
21 matches
Mail list logo
