All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Benjamin Herrenschmidt <benh@au1.ibm.com>
Cc: Stewart Smith <stewart@linux.vnet.ibm.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: REST API docs
Date: Thu, 3 Aug 2017 01:13:56 -0500	[thread overview]
Message-ID: <20170803061356.GI14987@asimov> (raw)
In-Reply-To: <1501719587.2664.15.camel@au1.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

On Thu, Aug 03, 2017 at 10:19:47AM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2017-08-02 at 08:01 -0500, Patrick Williams wrote:
> > 
> > Generally speaking, docs are for stable releases, aren't they? 
> 
> Certainly not !
> 
> You cannot change an API in a backward compatible way and keep the doc
> documenting the old/wrong way in the repo. That's just plain wrong.
> 
> Ben.
> 

Fair enough.  I honestly though calling this entire code stream 1.99.x
was sufficient "hear be dragons" to prevent people from coding to things
unless they speak up.  We've been actively engaging the teams that we
knew were affected by all of our API changes, and we were not aware of
this one.  The teams we keep informed outside of the direct development
community are: openbmc test-automation team, xCAT, and the GUI
development team.

I will make sure we go through the docs repository soon and clearly point
out everything that is deprecated in the 1.99.x code stream as such.

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-08-03  6:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  5:07 REST API docs Stewart Smith
2017-08-01 21:28 ` Patrick Williams
2017-08-02  7:02   ` Stewart Smith
2017-08-02 13:01     ` Patrick Williams
2017-08-03  0:19       ` Benjamin Herrenschmidt
2017-08-03  6:13         ` Patrick Williams [this message]
2017-08-03  7:34           ` Benjamin Herrenschmidt
2017-08-03  0:22       ` Benjamin Herrenschmidt
2017-08-03  6:08         ` Patrick Williams
2017-08-03  7:31           ` Benjamin Herrenschmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170803061356.GI14987@asimov \
    --to=patrick@stwcx.xyz \
    --cc=benh@au1.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.