Thanks for the pointers, everybody.

> -----Original Message-----
> From: Christopher Price [mailto:christopher.pr...@ericsson.com]
> Sent: Monday, October 17, 2016 4:18 PM
> To: O Mahony, Billy <billy.o.mah...@intel.com>; 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>
> Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs]
> Documentation updates for Colorado 2.0
> 
> Hi Billy,
> 
>     - Do I need to update all references/links in my documentation that reads 
> '
> colorado/docs' to 'colorado/2.0/docs' ?
> Yes, if you have direct links like this.  (this need is to be solved for 
> Danube)
>     - Do I check these git patches in to master?
> Yes.
>     - Do I then cherry-pick these changes to Colorado?
> Yes.
>     - Do I need to tag Colorado branch with Colorado2.0? When is this to be
> done?
> Yes. When you are ready, maybe David has the dates available.
>     - What does step 4. 'Re-merge' mean?
> Once the labels are put in the git the docs toolchain will label the final
> artifacts with that specific git label.  Doing a “remerge” on that final 
> labelled
> commit will update this.
>     - Anything else?
> Nope that’s about it.
> 
> / chris
> 
> On 2016-10-17, 15:56, "opnfv-tech-discuss-boun...@lists.opnfv.org on
> behalf of O Mahony, Billy" <opnfv-tech-discuss-boun...@lists.opnfv.org on
> behalf of billy.o.mah...@intel.com> wrote:
> 
>     Hi Sofia,
> 
>     I am standing in for Mark Gray as OVSNFV PTL while he is on vacation.
> 
>     We are not making any documentation changes for colorado2.0.
> 
>     Can you clarify the actions I need to take regarding to the doc updates 
> for
> Colorado2.0 as the link as the advice below seems to be in conflict.
> 
>     - Do I need to update all references/links in my documentation that reads 
> '
> colorado/docs' to 'colorado/2.0/docs' ?
>     - Do I check these git patches in to master?
>     - Do I then cherry-pick these changes to Colorado?
>     - Do I need to tag Colorado branch with Colorado2.0? When is this to be
> done?
>     - What does step 4. 'Re-merge' mean?
>     - Anything else?
> 
>     Thanks,
>     Billy.
> 
> 
> 
>     > -----Original Message-----
>     > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
>     > discuss-boun...@lists.opnfv.org] 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>
>     > Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs]
>     > Documentation updates for Colorado 2.0
>     >
>     > Quick edit,
>     >
>     > > 2, Cherrypick to Colorado 2.0
>     >
>     > is just Cherrypick to Colorado
>     >
>     > The remerge is what does the work, as all documentation merged after
> the
>     > colorado release will be put in the 2.0 folder.
>     >
>     > -Aric
>     >
>     >
>     > On Thu, Oct 13, 2016 at 7:41 AM, Sofia Wallin
> <sofia.wal...@ericsson.com>
>     > wrote:
>     > > Thank you Jonas for clarifying!
>     > >
>     > >
>     > >
>     > > All project must re-merge their documentation so that it gets updated
>     > > to Colorado.2.0.
>     > >
>     > >
> http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/documentation/i
>     > > ndex.html
>     > >
>     > > No matter if any updates has been made or not.
>     > >
>     > >
>     > >
>     > > How to do it,
>     > >
>     > > 1, Do your editorial updates and/or link updates
>     > >
>     > > 2, Cherrypick to Colorado 2.0
>     > >
>     > > 3, Tag according to tagging procedure
>     > >
>     > > 4, Re-merge
>     > >
>     > >
>     > >
>     > > BR,
>     > >
>     > > Sofia
>     > >
>     > >
>     > >
>     > >
>     > >
>     > > From: Jonas Bjurel
>     > > Sent: den 11 oktober 2016 23:21
>     > > To: Sofia Wallin <sofia.wal...@ericsson.com>;
>     > > opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV
>     > > (opnfv-tech-discuss@lists.opnfv.org)
>     > > <opnfv-tech-discuss@lists.opnfv.org>;
>     > > Fatih Degirmenci <fatih.degirme...@ericsson.com>; Ryota
>     > > <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 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 name-space change propagates through all links.
>     > >
>     > > BR/Jonas
>     > >
>     > >
>     > >
>     > > From: opnfv-tech-discuss-boun...@lists.opnfv.org
>     > > [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of
> Sofia
>     > > Wallin
>     > > Sent: Monday, October 10, 2016 4:46 PM
>     > > To: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV
>     > > (opnfv-tech-discuss@lists.opnfv.org)
>     > > <opnfv-tech-discuss@lists.opnfv.org>
>     > > Subject: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs]
>     > > Documentation updates for Colorado 2.0
>     > >
>     > >
>     > >
>     > > Please note that if any documentation has been updated for Colorado
>     > > 2.0 links in the OPNFV overall documents might need to be updated as
>     > well.
>     > >
>     > > Let me know what updates that has been done and/or if you plan to do
>     > > any updates.
>     > >
>     > >
>     > >
>     > > BR,
>     > >
>     > > Sofia
>     > >
>     > >
>     > >
>     > > From: opnfv-project-leads-boun...@lists.opnfv.org
>     > > [mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of
>     > > Sofia Wallin
>     > > Sent: den 6 oktober 2016 14:16
>     > > To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org)
>     > > <opnfv-tech-discuss@lists.opnfv.org>;
>     > > opnfv-project-le...@lists.opnfv.org
>     > > Subject: [opnfv-project-leads] [opnfvdocs] [opnfv-tech-discuss]
>     > > Version control for generated documents
>     > >
>     > >
>     > >
>     > > Hi,
>     > >
>     > > In order to preserve the documents released as part of colorado.1.0,
>     > > the location to store colorado.2.0 documents have been changed.
>     > >
>     > > The new location adds version string into the path. For example, the
>     > > top level colorado.1.0 release documentation was stored and linked as
>     > below.
>     > >
>     > >
> http://artifacts.opnfv.org/opnfvdocs/colorado/docs/documentation/index
>     > > .html
>     > >
>     > >
>     > >
>     > > This now changed to for any updates that might come for this
> document.
>     > >
>     > >
> http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/documentation/i
>     > > ndex.html
>     > >
>     > >
>     > >
>     > > If you plan to do documentation updates as part of colorado.2.0, you
>     > > should update the links/references  in them accordingly.
>     > >
>     > > This is a step towards applying version control for our generated
>     > > documents and same change will be applied for colorado.3.0 as well.
>     > >
>     > >
>     > >
>     > > Let me know if you have any questions.
>     > >
>     > >
>     > >
>     > > BR,
>     > >
>     > > Sofia
>     > >
>     > >
>     > > _______________________________________________
>     > > opnfv-tech-discuss mailing list
>     > > opnfv-tech-discuss@lists.opnfv.org
>     > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>     > >
>     > _______________________________________________
>     > opnfv-tech-discuss mailing list
>     > opnfv-tech-discuss@lists.opnfv.org
>     > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>     _______________________________________________
>     opnfv-tech-discuss mailing list
>     opnfv-tech-discuss@lists.opnfv.org
>     https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to