Date   
Reminder Deadline Feb 28th: Invitation for FD.io Project Proposals to LFN Mentorship Program

Trishan de Lanerolle
 

We’re excited to open the call for mentors and project proposals for the 2020 LF Networking Mentorship Program. This is the first year we're bringing all community intern/mentor projects, under an integrated program schedule. This is intended to provide a formal structure to connect mentors and student developers from around the globe, to contribute their enthusiasm, time, and experience toward building sustainable LFN communities.

  I am interested in mentoring but how do I get started? 

Why should you consider mentoring for LF Networking Mentorship Program?
  • You believe in the value of mentorship in helping new developers to navigate open source development, the culture, the tooling and infrastructure to be a productive member of the community.  
  • You are passionate about teaching and guiding student developers, many of whom may be first time open-source contributors, 
  • You are eager to bring in new perspectives, new ideas, and new talent into your community and projects.
  • You have a narrowly scoped mentorship project with clear learning objectives/outcomes and a mentee's work and potential contributions could add value to the project or community of which you're an active developer or maintainer.     

What are the elements the LFN Mentorship Program will implement to maximize mentor/mentee collaboration success?
  • Mentor and mentee onboarding will be conducted at the start of the Program
  • Mentor and mentee guide will be available as part of the Linux Foundation CommunityBridge Mentorship initiative
  • Project planning that includes deliverables, milestones, and tasks will be completed collaboratively between the mentors and mentees during the first two weeks of the program and posted on the wiki to increase transparency and accountability.
  • Mentee presentations will be required to sharpen both presentation skills and to cultivate the ability to provide constructive feedback and critique that’s the norm in the open source community for developing technologies collaboratively and openly.
  • Mentee evaluation will be conducted on a regular cadence tied to milestone deliverable schedules to help mentors and LFN staff formalize and respond to progress.
While mentors will be on a voluntary basis, the hired mentees will be eligible to receive a stipend. As an added bonus, each mentee who successfully completes the Program will be invited and financially sponsored by LF Networking to attend an event/conference and present their work to the broader community (specific event TBD but will be during Q3 or Q4 of this year or Q1 of the following year).

If you have any questions, please contact mentorship@...

We look forward to your submission of a mentorship project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the LF Networking communities.

--
Trishan R. de Lanerolle
Technical Program Manager & Community Architect 
Networking, Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle

Invitation for FD.io Project Proposals to LFN Mentorship Program

Trishan de Lanerolle
 

We’re excited to open the call for mentors and project proposals for the 2020 LF Networking Mentorship Program. This is the first year we're bringing all community intern/mentor projects, under an integrated program schedule. This is intended to provide a formal structure to connect mentors and student developers from around the globe, to contribute their enthusiasm, time, and experience toward building sustainable LFN communities.

  I am interested in mentoring but how do I get started? 

Why should you consider mentoring for LF Networking Mentorship Program?
  • You believe in the value of mentorship in helping new developers to navigate open source development, the culture, the tooling and infrastructure to be a productive member of the community.  
  • You are passionate about teaching and guiding student developers, many of whom may be first time open-source contributors, 
  • You are eager to bring in new perspectives, new ideas, and new talent into your community and projects.
  • You have a narrowly scoped mentorship project with clear learning objectives/outcomes and a mentee's work and potential contributions could add value to the project or community of which you're an active developer or maintainer.     

What are the elements the LFN Mentorship Program will implement to maximize mentor/mentee collaboration success?
  • Mentor and mentee onboarding will be conducted at the start of the Program
  • Mentor and mentee guide will be available as part of the Linux Foundation CommunityBridge Mentorship initiative
  • Project planning that includes deliverables, milestones, and tasks will be completed collaboratively between the mentors and mentees during the first two weeks of the program and posted on the wiki to increase transparency and accountability.
  • Mentee presentations will be required to sharpen both presentation skills and to cultivate the ability to provide constructive feedback and critique that’s the norm in the open source community for developing technologies collaboratively and openly.
  • Mentee evaluation will be conducted on a regular cadence tied to milestone deliverable schedules to help mentors and LFN staff formalize and respond to progress.
While mentors will be on a voluntary basis, the hired mentees will be eligible to receive a stipend. As an added bonus, each mentee who successfully completes the Program will be invited and financially sponsored by LF Networking to attend an event/conference and present their work to the broader community (specific event TBD but will be during Q3 or Q4 of this year or Q1 of the following year).

If you have any questions, please contact mentorship@...

We look forward to your submission of a mentorship project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the LF Networking communities.

--
Trishan R. de Lanerolle
Technical Program Manager & Community Architect 
Networking, Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle

VPP 19.08 artifacts deferral notice and 19.08.1 schedule

Dave Wallace
 

Dear FD.io Project Members,

[ Note: FD.io <project>-dev email lists BCC'd to reduce noise ]

As discussed in this week's VPP Bi-Weekly Community Meeting, there
is the necessity to introduce a critical fix that breaks VPP API
compatibility. Therefore we need to defer ALL 19.08 release artifacts
and publish 19.08.1 as soon as practicable.

We apologize in advance for this inconvenience. The details are
in the VPP 19.08.1 release note change set [0].

We plan to merge the API-breaking fix into stable/1908 on Monday
9 September 2019 at 9am CET, and would like to cut the VPP 19.08.1
release on Thursday 12 September. The timing is rather tight to
avoid accumulating too many additional commits to stable/1908 and
to minimize the changes between 19.08 and 19.08.1.

Please review the release note change set [0] and add yourself as
a reviewer to be informed of any changes to the plan.

PTLs, please indicate that your project is okay with these dates or
add your desired dates on-gerrit and save the changes to [0].

We would also kindly ask that even if you are okay with these dates,
that you add 1 or 2 persons from your project as reviewers to [0],
to be able to efficiently communicate any changes to the plan to all
interested project teams.

Thanks,
Andrew & Dave
"Your Friendly VPP Release Managers"

[0] https://gerrit.fd.io/r/#/c/vpp/+/21829/

FD.io - Gerrit 2.16 Changes

Vanessa Valderrama
 

Changes that will happen with Gerrit:

1) The 'New UI' for Gerrit will become the default UI

2) The Draft work flow is removed and replaced with 'Work in Progress'
aka 'WIP' and 'Private' workflows. Unfortunately git-review does not
support either of these workflows directly. Utilizing them means either
pushing your changes the manual way for either system or pushing them up
with git-review and then marking the change via the UI into either of
the workflows.

To push a private change you may do so as follows:
git push origin HEAD:refs/for/master%private

To pull it out of private you may do so as follows:
git push origin HEAD:refs/for/master%remove-private

To push a WIP you may do so as follows:
git push origin HEAD:refs/for/master%wip

To mark it ready for review you may do so as follows:
git push origin HEAD:refs/for/master%ready

Once a change is in either private or WIP state it does not switch the
change to a ready state until the current state has been removed.

In both cases, the state can be set via the UI by selecting the tripple
dot menu option on the change and selecting the appropriate option.

To remove WIP state press the 'START REVIEW' button. To remove the
private state you must do so via the menu.

NOTE: We are not moving to Gerrit 3 at this time. That is on the road
map but we need to come to the latest 2.x as we have to do various
migrations that are only available at the 2.16 level before we can move
to Gerrit 3.

Thank you,
Vanessa

LF Service Desk ticketing changes

Trishan de Lanerolle
 

Service Desk migration

The Linux Foundation IT is migrating from email-based support system using Request Tracker to a web-based platform provided by Jira Service Desk. We are doing this in order to improve our level of service and your support experience.


The following are the primary improvements you should expect after migration is complete:


  1. Single Sign-On with other Linux Foundation sites, using the same LF ID credentials

  2. Integration with knowledge base articles to help identify possible self-service solutions

  3. Ability to track all your support requests across various projects via the same service desk interface

  4. Ability to see public issues created by other members of your project


The new service desk will become available to you starting Monday, June 17, 2019.


Any support requests that are already open in RT will be preserved and completed there, so there is no need to re-submit them again using the Jira Service Desk. Any new tickets created in RT will be automatically closed with a suggestion and instructions to use the new service desk procedure.


Starting Monday, June 17, please use the procedure described in the attached “Getting LF IT Help” document.


If you need help with anything IT-related for your FD.io project, please use our Service Desk
platform to open a support request: https://
support.linuxfoundation.org



Call for 2019 FD.io Internship Projects and Mentors

Trishan de Lanerolle
 

FD.io Technical Community,

We’re excited to open the call for the 2019 internship mentors and project ideas. We’re looking to sponsor four internship projects this year.

LFN Internships are for University or College students who are interested in contributing to real-world impactful Networking Open Source projects. Each intern will be working with a mentor from the FD.io project community to complete a project either in 3 months (full time 40 hours a week) or 6 months (part time 20 hours a week). This is a paid internship program that accepts applications throughout the year and the internship projects usually start on a quarterly schedule. As an open source project, each intern will work remotely from his or her location of choice.

If you’ve identified a project or task that’s suitable for an internship project and you’re interested in mentoring a student developer, please define the project by completing the internship project proposal template on the wiki by April 10th. (https://wiki.fd.io/view/Interns/Projects )

A few things to note as you plan to submit a project for consideration:
  • Multiple mentors supervising one intern per project would be desirable as this helps spread the workload and reduce the challenge of coverage caused by working remotely with an intern in a different time zone.
  • The mentor(s) need to be familiar with the project and is/are expected to directly supervise the intern’s technical work.
  • The proposed project needs to be clearly scoped and structured to be suitable for an internship project.
  • The project should be related to one of the current FD.io projects or tools.

Interns will be eligible to receive a stipend. The stipend will be paid in several installments provided that regular interval evaluations show the intern is making satisfactory progress. Additional details about LFN internships are available here

We look forward to your submission of a project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the FD.io community.

Regards,
Trishan












--
Trishan R. de Lanerolle
Program Manager,  Networking
Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle

Invitation to report out to the TSC

Trishan de Lanerolle
 

Hi,
The FD.io TSC would like to extend an invitation to community projects to provide a status updates on work, anticipated roadmap or any challenges they are working through. We hope this will be an opportunity to gain additional insights into the great work going on within our diverse community of projects. 

Please sign up for a slot and designate your project lead/representative for the meeting day of your choice.  


Anticipate one project to present per week.  A short presentation (10-12 minutes) during the weekly TSC call.  The TSC calls are always open to the community to attend. 

Regards, 
Trishan 





--
Trishan R. de Lanerolle
Program Manager,  Networking
Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle

Re: [vpp-dev] IRC SPAM

Burt Silverman <burtms@...>
 

I registered and verified, but when I try to log in I always go to the unregistered area. How do I log in now? The instructions are pretty useless for a non SASL client user.

Burt

On Wed, Aug 22, 2018 at 12:49 PM, Vanessa Valderrama <vvalderrama@...> wrote:

In effort to prevent IRC SPAM we are requiring registration in the FD.io channels. 

Thank you,
Vanessa

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

View/Reply Online (#10257): https://lists.fd.io/g/vpp-dev/message/10257
Mute This Topic: https://lists.fd.io/mt/24921658/541103
Group Owner: vpp-dev+owner@...
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [burtms@...]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [nsh_sfc-dev] IRC SPAM

Joel M. Halpern <jmh@...>
 

Specifically, when I try to use the /connect command the instructions call for I get: Permission Denied - You're not an IRC operator

Yours,
Joel

On 8/22/18 12:49 PM, Vanessa Valderrama wrote:
In effort to prevent IRC SPAM we are requiring registration in the FD.io channels.
* The following channels will require registration to join the channel
o https://wiki.fd.io/view/IRC
* Please follow these steps to register on Freenode
o https://freenode.net/kb/answer/registration
Thank you,
Vanessa
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#636): https://lists.fd.io/g/nsh_sfc-dev/message/636
Mute This Topic: https://lists.fd.io/mt/24921652/675455
Group Owner: nsh_sfc-dev+owner@...
Unsubscribe: https://lists.fd.io/g/nsh_sfc-dev/unsub [jmh@...]
-=-=-=-=-=-=-=-=-=-=-=-

IRC SPAM

Vanessa Valderrama
 

In effort to prevent IRC SPAM we are requiring registration in the FD.io channels. 

Thank you,
Vanessa

Migration to Groups.io tomorrow morning 2/08

Brendan OSullivan <bosullivan@...>
 

Greetings FD.io community!

We apologize for the relatively late notice, as this normally would have been communicated earlier.

The Linux Foundation has connected with a new vendor called Groups.io, which provides mailing list services in a simple but modern interface. Groups.io offers all of the capabilities of our existing Mailman mailing service plus additional community tools that make it an exceptional service solution.


We are planning to set your project up with Groups.io service and migrate your existing mailing list archives and user lists, including preferences, tomorrow morning February 8th.


During the migration window you will still be able to access the archives, however the delivery of messages sent to the mailing lists during this window will be delayed until after the migration of the archives and list members are complete. We will turn off new list signups during the migration window, then this functionality will be restored once it is complete.


FAQs

What are the key differences between Mailman and Groups.io?

  • Groups.io has a modern interface, robust user security model, and interactive, searchable archives

  • Groups.io provides advanced features including muting threads and integrations with modern tools like GitHub, Slack, and Trello

  • Groups.io also has optional extras like a shared calendar, polling, chat, a wiki, and more

  • Groups.io uses a concept of subgroups, where members first join the project “group” (a master list), then they choose the specific “subgroup” lists they want to subscribe to


How do the costs compare?

  • The Linux Foundation can provide project-branded Groups.io accounts to projects for less cost than managing our in-house Mailman systems.


How is the experience different for me as a list moderator or participant?

In many ways, it is very much the same. You will still find the main group at your existing URL and sub-groups equate to the more focused mailing lists based on the community’s needs.


Here is an example of main group and sub-group URL patterns, and their respective emails:


https://lists.projectname.org/g/main

https://lists.projectname.org/g/devs

https://lists.projectname.org/g/ci

main@...

devs@...

ci@...


One of the nice features of Groups.io is that you log in once, and can use the My Groups dropdown in the top menu and easily move between the lists that you are participating in without logging in to each of them separately.


Groups.io’s simple but highly functional UI that will make the experience of moderating or participating in the community discussions more enjoyable.


If you’d like to learn more about using Groups.io , please reference their help documentation. If you need assistance with Groups.io, please email helpdesk@... for The Linux Foundation’s helpdesk.


Cheers!
Brendan OSullivan

Helpdesk Analyst

Re: CFP for fd.io Minisummit at OpenStack Summit, Monday, May 8 Boston

Edward Warnicke
 

Apologies, the last email was sent prematurely, the link to information and to the CFP form to submit talks is here:


On Mon, Mar 27, 2017 at 11:09 AM, Ed Warnicke <hagbard@...> wrote:
fd.io is having a minisummit at the OpenStack Summit Monday May 8 in Boston, MA.

The Call for Papers (CFP) has opened, and you can find a link to it here:


CFP for fd.io Minisummit at OpenStack Summit, Monday, May 8 Boston

Edward Warnicke
 

fd.io is having a minisummit at the OpenStack Summit Monday May 8 in Boston, MA.

The Call for Papers (CFP) has opened, and you can find a link to it here:

Happy Solstice and holidays!

David Ward (wardd) <wardd@...>
 

All -

Given the holiday today, I’ll wax a bit on the accomplishments of fd.io over the last 12 months.  February 11, 2016, fd.io launched.  It's purpose was to build the software dataplane for the next Internet architectural constructs.  Something so high performance, scalable, and flexible that it could not only meet the unmet needs of today, but the unknown needs of the future.
 
In the brief time since its birth, the fd.io community has grown to 13 subprojects with over 130 contributors from over 30 different organizations.   Across the fd.io community, over 4600 commits have occurred since launch, leading to two (soon to be three) successful releases.
 
The community has held two trainings and two minisummits on two different continents.  fd.io has developed an ecosystem of interest from OpNFV, to ODL to Calico, with real integrations backing up those interests.
 
Everyday fd.io supports valuable new features and everyday its performance and scale improves.
 
fd.io is succeeding beyond the grandest imagination of its founding.  Its' succeeding because of the blood, sweet and tears all of you in the fd.iocommunity have put in and continue to put into it.  The mental effort, programming prowess, code style coming from late nights, weekends, travel, and the stress.  But also the brilliance, the creativity, the resolve, and the passion.  Its succeeding because because of you.
 
Thanks

-DWard (Chairman of fd.io board)

[it-infrastructure-alerts] CI infrastructure issues for FD.io and Zephyr Project

Edward Warnicke
 

FYI...
---------- Forwarded message ----------
From: Andrew Grimberg <agrimberg@...>
Date: Thu, Oct 6, 2016 at 12:27 PM
Subject: [it-infrastructure-alerts] CI infrastructure issues for FD.io and Zephyr Project
To: IT Infrastructure Alerts <it-infrastructure-alerts@...>
Cc: infra-steering@..., discuss@..., devel@...


Greetings folks,

As many of you may already be aware, we've been experiencing some issues
with the CI environments for both FD.io and Zephyr Project over the
course of the last couple of days.

The problems have been caused by a couple of different issues and our
cloud provider has appears to have resolved all but one of them at this
point.

The issue currently facing both environments is that the default gateway
v-router does not appear to be actually passing traffic the way it's
supposed to be. Because of this Jenkins is unable to presently
communicate with the cloud API for bringing new instances online. It
also means that it can't actually get to Gerrit. As such, presently
Jenkins is not seeing new changes come in.

We do not presently have an ETA on the resolution to this particular
issue. Once the routing issue is cleared the environments should start
operating again.

-Andy-

--
Andrew J Grimberg
Systems Administrator
Release Engineering Team Lead
The Linux Foundation

--
You received this message because you are subscribed to the Google Groups "IT Infrastructure Alerts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to it-infrastructure-alerts+unsubscribe@linuxfoundation.org.

Re: [csit-dev] Proposed presentation template for fd.io

Keith Burns <alagalah@...>
 

Mate,

That's great feedback... I didn't just wake up and decide I was the arbiter of good taste... I did discuss this with a few people first and ran my proposal by them for thumbs up/down.

My only ask then is that we give back to the community by allowing the Blood Bank to place drip trays at audience members feet ... :-P

... and with that, I shan't make any more jokes. 

If the general consensus is that what we have is perfectly fine, all good.

On Tue, Sep 20, 2016 at 9:33 AM St Leger, Jim <jim.st.leger@...> wrote:

Keith:

 

Respectfully, the look/feel of FD.io was laid out some time ago around the project’s inception and some subsequent meetings.  There is a small marketing sub-committee of people who worked on it with some help form the LF’s marketing folks.

 

If there’s consensus that the current presentation template isn’t working or doesn’t represent the project well then let’s let that team work on improving it.

Omar was the Cisco rep, though I don’t know if he still is (or if no, who is today.)

John DiGiglio is the Intel rep (Ray was covering while John was out.)

I don’t know who else is involved, but John can chime in w/the LF lead name and perhaps other folks.

 

My two cents.

Jim

 

 

 

From: csit-dev-bounces@... [mailto:csit-dev-bounces@...] On Behalf Of Keith Burns
Sent: Tuesday, September 20, 2016 9:24 AM
To: vpp-dev <vpp-dev@...>; tsc@...; discuss@...; nsh_sfc-dev@...; csit-dev@...; honeycomb-dev@...; one-dev@...; tldk-dev@...; deb-dpdk@...; trex-dev@...
Subject: [csit-dev] Proposed presentation template for fd.io

 

Hello,

 

I realised that every time I looked at an fd.io presentation my eyes started to bleed. 

 

Given the summit is just a few days away, I know this maybe a little short notice, but I started on my preso last week and found I was going through a box of Kleenex and a pint of blood per slide (see "eyes bleed").

 

I put together a preliminary template I'd like to propose for comment, Kleenex preservation and general ocular safety.

 

I think it has sufficient layouts (as in not many) for nearly all presentation use cases.

 

I also selected the font sizes based on forcing folks to not produce eyecharts/whitepapers in PPT form. ("horse", "water", "too big to drown" etc).

 

 

It is in google docs format at the moment, so I can almost guarantee it won't translate to Microsoft PPT well but if folks like it I will:

 

1. Create a PPT format and link both on the wiki

2. Create some commonly used icons and a color palette I came up with for said icons that works with this theme (as per some web design "Best of " type thing fastcodesign.com)

 

 

Re: [csit-dev] Proposed presentation template for fd.io

St Leger, Jim <jim.st.leger@...>
 

Keith:

 

Respectfully, the look/feel of FD.io was laid out some time ago around the project’s inception and some subsequent meetings.  There is a small marketing sub-committee of people who worked on it with some help form the LF’s marketing folks.

 

If there’s consensus that the current presentation template isn’t working or doesn’t represent the project well then let’s let that team work on improving it.

Omar was the Cisco rep, though I don’t know if he still is (or if no, who is today.)

John DiGiglio is the Intel rep (Ray was covering while John was out.)

I don’t know who else is involved, but John can chime in w/the LF lead name and perhaps other folks.

 

My two cents.

Jim

 

 

 

From: csit-dev-bounces@... [mailto:csit-dev-bounces@...] On Behalf Of Keith Burns
Sent: Tuesday, September 20, 2016 9:24 AM
To: vpp-dev <vpp-dev@...>; tsc@...; discuss@...; nsh_sfc-dev@...; csit-dev@...; honeycomb-dev@...; one-dev@...; tldk-dev@...; deb-dpdk@...; trex-dev@...
Subject: [csit-dev] Proposed presentation template for fd.io

 

Hello,

 

I realised that every time I looked at an fd.io presentation my eyes started to bleed. 

 

Given the summit is just a few days away, I know this maybe a little short notice, but I started on my preso last week and found I was going through a box of Kleenex and a pint of blood per slide (see "eyes bleed").

 

I put together a preliminary template I'd like to propose for comment, Kleenex preservation and general ocular safety.

 

I think it has sufficient layouts (as in not many) for nearly all presentation use cases.

 

I also selected the font sizes based on forcing folks to not produce eyecharts/whitepapers in PPT form. ("horse", "water", "too big to drown" etc).

 

 

It is in google docs format at the moment, so I can almost guarantee it won't translate to Microsoft PPT well but if folks like it I will:

 

1. Create a PPT format and link both on the wiki

2. Create some commonly used icons and a color palette I came up with for said icons that works with this theme (as per some web design "Best of " type thing fastcodesign.com)

 

 

Proposed presentation template for fd.io

Keith Burns <alagalah@...>
 

Hello,

I realised that every time I looked at an fd.io presentation my eyes started to bleed. 

Given the summit is just a few days away, I know this maybe a little short notice, but I started on my preso last week and found I was going through a box of Kleenex and a pint of blood per slide (see "eyes bleed").

I put together a preliminary template I'd like to propose for comment, Kleenex preservation and general ocular safety.

I think it has sufficient layouts (as in not many) for nearly all presentation use cases.

I also selected the font sizes based on forcing folks to not produce eyecharts/whitepapers in PPT form. ("horse", "water", "too big to drown" etc).


It is in google docs format at the moment, so I can almost guarantee it won't translate to Microsoft PPT well but if folks like it I will:

1. Create a PPT format and link both on the wiki
2. Create some commonly used icons and a color palette I came up with for said icons that works with this theme (as per some web design "Best of " type thing fastcodesign.com)


Re: [nsh_sfc-dev] VPP 16.09 release artifacts published

Ni, Hongjun <hongjun.ni@...>
 

Good news!   Congratulations!

 

From: nsh_sfc-dev-bounces@... [mailto:nsh_sfc-dev-bounces@...] On Behalf Of Keith Burns
Sent: Saturday, September 17, 2016 9:08 AM
To: vpp-dev <vpp-dev@...>; discuss@...; csit-dev@...; honeycomb-dev@...; nsh_sfc-dev@...; one-dev@...; C.J. Collier <cjcollier@...>
Subject: [nsh_sfc-dev] VPP 16.09 release artifacts published

 

Packages: https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages

 

(Note: for some reason these have not updated but assuming that will happen over weekend.)

 

Thanks Ed and CJ with all the help with the release process.

 

 

 

Re: [discuss] VPP 16.09 relpease artifacts published

Leonid <leonid.grossman@...>
 

6poo



Sent from my Verizon Wireless 4G LTE smartphone


-------- Original message --------
From: Keith Burns <alagalah@...>
Date: 2016/09/16 6:07 PM (GMT-08:00)
To: vpp-dev <vpp-dev@...>, discuss@..., csit-dev@..., honeycomb-dev@..., nsh_sfc-dev@..., one-dev@..., "C.J. Collier" <cjcollier@...>
Subject: [discuss] VPP 16.09 release artifacts published

Packages: https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages

(Note: for some reason these have not updated but assuming that will happen over weekend.)

Thanks Ed and CJ with all the help with the release process.