From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 8193A2C7A for ; Thu, 12 Feb 2015 10:03:26 +0100 (CET) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t1C93POT032388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Thu, 12 Feb 2015 04:03:25 -0500 Received: from localhost.localdomain (vpn1-5-97.ams2.redhat.com [10.36.5.97]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t1C93O7j008040 for ; Thu, 12 Feb 2015 04:03:25 -0500 Message-ID: <54DC6C5C.6020005@redhat.com> Date: Thu, 12 Feb 2015 11:03:24 +0200 From: Panu Matilainen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: dev@dpdk.org References: <20150212070635.GA31227@mhcomputing.net> In-Reply-To: <20150212070635.GA31227@mhcomputing.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 Subject: Re: [dpdk-dev] Previous DPDK version API documentation for app developers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 09:03:27 -0000 On 02/12/2015 09:06 AM, Matthew Hall wrote: > Hi all, > > I ran into a funny situation today with the API documentation. > > For stability until I can get my app mostly working, I was using DPDK 1.7.X, > so I could concentrate on making the app reliable. But the DPDK website only > has the API docs for DPDK 1.8.X / HEAD. > > I was wondering if we could have copies of the most recent few versions in the > site, and some scripts or steps to regenerate locally so you can get the > matching version in the local machine. Same goes for release notes: old versions should be kept around and preferably at the original url, which requires them to be versioned from the start. - Panu -