2015-08-11 15:28, Thomas Monjalon:
> 2015-08-11 13:12, Mcnamara, John:
> > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > > Why not add faq after user guides and before release notes and
> > > contributor's guidelines?
> > > user guides
> > > faq
> > > release notes
> > >
2015-08-11 13:12, Mcnamara, John:
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > Why not add faq after user guides and before release notes and
> > contributor's guidelines?
> > user guides
> > faq
> > release notes
> > contributing
>
> Hi,
>
> No strong
2015-08-11 12:57, John McNamara:
> --- a/doc/guides/index.rst
> +++ b/doc/guides/index.rst
> @@ -46,3 +46,4 @@ Contents:
> testpmd_app_ug/index
> rel_notes/index
> guidelines/index
> + faq/index
Why not add faq after user guides and before release notes and
contributor's guidelines?
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Tuesday, August 11, 2015 2:02 PM
> To: Mcnamara, John
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: restructured release notes
> documentation
>...
> Why no
Restructured the Release Notes documentation into a more useful structure
that is easier to use and to update between releases.
The main changes are:
* Each release version has it's own section with New Features,
Resolved Issues, Known Issues and API/ABI Changes.
* Redundant sections
5 matches
Mail list logo
