>
> Cc: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV (opnfv-tech-
> disc...@lists.opnfv.org) <opnfv-tech-discuss@lists.opnfv.org>
> Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs]
> Documentation updates for Colorado 2.0
>
> Hi Billy,
>
] On Behalf Of Aric Gardner
> > Sent: Thursday, October 13, 2016 2:47 PM
> > To: Sofia Wallin <sofia.wal...@ericsson.com>
> > Cc: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV (opnfv-tech-
> > disc...@lists.opnfv.org) <opnfv-tech-discuss@lists.opnfv.org>
>
t; <r-m...@cq.jp.nec.com>; David McBride <dmcbr...@linuxfoundation.org>;
> Christopher Price <christopher.pr...@ericsson.com>
> Subject: RE: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs]
> Documentation updates for Colorado 2.0
>
>
>
> Adding to Sof
ice
<christopher.pr...@ericsson.com>
Subject: RE: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs]
Documentation updates for Colorado 2.0
Adding to Sofia's point, please be aware that any documentation built for the
Colorado 2.0 release will end up in a different OPNFV artifac
Adding to Sofia's point, please be aware that any documentation built for the
Colorado 2.0 release will end up in a different OPNFV artifacts name-space.
This means that links have to be reviewed and verified.
And in many case this means a complete new docs set for the projects - as the
