> On 14 Nov 2018, at 14:47, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at 
> Cisco) via Lists.Fd.Io <[email protected]> wrote:
> 
> > email = [email protected]
> > email = [email protected]
>  
> I think it would be easier to sent only one e-mail
> to a fd.io mailing list created specifically
> for announcing VPP api changes.
> Similarly to how we created csit-report [0]
> for announcing performance testing results.
>  
> That way the interested parties can subscribe
> (without the need to edit project configuration).
>  
> > additional hoops may need to be navigated depending on the receiver.
>  
> It is easier to make this work
> when there is only one receiver (the new mailing list).

Yes, a vpp-api-notify list or something. Then interested parties could 
subscribe to that.

Thanks a lot Ed!
What more needs to be set into action for this one?

Cheers,
Ole

>  
> Vratko.
>  
> [0] https://lists.fd.io/g/csit-report
>  
> From: [email protected] <[email protected]> On Behalf Of Ed Kern via 
> Lists.Fd.Io
> Sent: Tuesday, 2018-November-13 22:29
> To: Ole Troan <[email protected]>
> Cc: [email protected]
> Subject: Re: [vpp-dev] API changes to trigger email
>  
> Should be able to… 
>  
> Not that I have the permissions to do it…
>  
> following 
> https://gerrit-review.googlesource.com/Documentation/user-notify.html#project
>  
> My first thought is you would want to end up with something along the lines of
>  
> [notify “API”]
> email = [email protected]
> email = [email protected]
> filter = path:^.*\.api
> header = to:
> type = submitted_changes
>  
>  
> submitted_changes for merges or new_changes  if you wanted to see potential 
> changes
>  
> My GUESS is that you would need at least a vpp committer to satisfy "To edit 
> the project level notify settings, ensure the project owner has Push 
> permission already granted for the refs/meta/config branch.”
> 
> 
> If it turns out you need something from the LF feel free to open a ticket 
> with them or just let me know and ill open it..
>  
> Hope this helps,
>  
> Ed
>  
> P.S.  This should SEND the email…of course additional hoops may need to be 
> navigated depending on the receiver..  Non member trying to post type bounces.
>  
> 
> 
> On Nov 13, 2018, at 5:41 AM, Ole Troan <[email protected]> wrote:
>  
> Eds, et al,
> 
> At some point in the past we discussed adding a trigger in gerrit to generate 
> an email alerting adjacency projects about VPP API changes.
> Basically any change in a .api file.
> 
> Is that something possible to do?
> 
> Best regards,
> Ole
>  
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#11250): https://lists.fd.io/g/vpp-dev/message/11250
> Mute This Topic: https://lists.fd.io/mt/28122200/675193
> Group Owner: [email protected]
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [[email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11256): https://lists.fd.io/g/vpp-dev/message/11256
Mute This Topic: https://lists.fd.io/mt/28122200/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
  • ... Ole Troan
    • ... Ed Kern via Lists.Fd.Io
      • ... Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io
        • ... Ole Troan

Reply via email to